PyQt unit test that QDialog is created The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) The Ask Question Wizard is Live! Data science time! April 2019 and salary with experiencePyQt4 User Input Validation - QlineEditWhere do the Python unit tests go?How can I safely create a nested directory in Python?Create a dictionary with list comprehension in PythonWriting unit tests in Python: How do I start?Is there a way to control how pytest-xdist runs tests in parallel?Have 2 pyqt buttons move synchronized when mouse movesHow to read all message from queue using stomp library in Python?Running into issues with PyOpenGL and PyQt5 on OSXEmbedding VTK object in PyQT5 windowmultiple gui python qt and switch between them
What was the last x86 CPU that did not have the x87 floating-point unit built in?
How to test the equality of two Pearson correlation coefficients computed from the same sample?
How to delete random line from file using Unix command?
How to politely respond to generic emails requesting a PhD/job in my lab? Without wasting too much time
Mortgage adviser recommends a longer term than necessary combined with overpayments
Can smartphones with the same camera sensor have different image quality?
What information about me do stores get via my credit card?
How is simplicity better than precision and clarity in prose?
Can a 1st-level character have an ability score above 18?
What do you call a plan that's an alternative plan in case your initial plan fails?
Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?
Match Roman Numerals
Why did all the guest students take carriages to the Yule Ball?
What is special about square numbers here?
Windows 10: How to Lock (not sleep) laptop on lid close?
Derivation tree not rendering
Didn't get enough time to take a Coding Test - what to do now?
Working through the single responsibility principle (SRP) in Python when calls are expensive
Scientific Reports - Significant Figures
First use of “packing” as in carrying a gun
When did F become S in typeography, and why?
Take groceries in checked luggage
Arduino Pro Micro - switch off LEDs
Keeping a retro style to sci-fi spaceships?
PyQt unit test that QDialog is created
The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
The Ask Question Wizard is Live!
Data science time! April 2019 and salary with experiencePyQt4 User Input Validation - QlineEditWhere do the Python unit tests go?How can I safely create a nested directory in Python?Create a dictionary with list comprehension in PythonWriting unit tests in Python: How do I start?Is there a way to control how pytest-xdist runs tests in parallel?Have 2 pyqt buttons move synchronized when mouse movesHow to read all message from queue using stomp library in Python?Running into issues with PyOpenGL and PyQt5 on OSXEmbedding VTK object in PyQT5 windowmultiple gui python qt and switch between them
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have a parent widget that in some cases calls a custom QDialog to get user input. How do I write a unit test to ensure the dialog is called, and that it will handle correct input correctly?
Here's a mini example:
from PyQt5.QtWidgets import QDialog, QVBoxLayout, QWidget, QLabel, QApplication
from PyQt5.Qt import pyqtSignal, QPushButton, pyqtSlot, QLineEdit
import sys
class PopupDialog(QDialog):
result = pyqtSignal(str)
def __init__(self):
super().__init__()
layout = QVBoxLayout(self)
self.setLayout(layout)
lbl = QLabel("That's not a full number! Try again?")
layout.addWidget(lbl)
self.field = QLineEdit(self)
layout.addWidget(self.field)
self.btn = QPushButton("Ok")
self.btn.clicked.connect(self.on_clicked)
layout.addWidget(self.btn)
def on_clicked(self):
value = self.field.text().strip()
self.result.emit(value)
self.close()
class Example(QWidget):
def __init__(self):
super().__init__()
self.init_UI()
def init_UI(self):
layout = QVBoxLayout()
self.setLayout(layout)
lbl = QLabel("Please provide a full number")
layout.addWidget(lbl)
self.counter_fld = QLineEdit(self)
self.counter_fld.setText("1")
layout.addWidget(self.counter_fld)
self.btn = QPushButton("start")
layout.addWidget(self.btn)
self.btn.clicked.connect(self.on_clicked)
self.field = QLabel()
layout.addWidget(self.field)
self.show()
@pyqtSlot()
def on_clicked(self):
txt = self.counter_fld.text()
self.dialog = None
try:
result = int(txt) * 100
self.field.setText(str(result))
except ValueError:
self.dialog = PopupDialog()
self.dialog.result.connect(self.catch_dialog_output)
self.dialog.exec_()
@pyqtSlot(str)
def catch_dialog_output(self, value):
self.counter_fld.setText(value)
self.on_clicked()
def main():
app = QApplication(sys.argv)
ex = Example()
ex.show()
sys.exit(app.exec_())
if __name__ == '__main__':
main()
So in this case, I'd want to write a unit test that inserts different values into self.field and then tests that it works without PopupDialog for integers but that the PopupDialog is called when inserting a string.
(I know I could just test the functionality without the dialog, and that for this problem, the QDialog is not actually needed. I just tried to keep the example simple. Baseline is: I can get the unit test through the steps until the popup dialog is created, but how can I then test that it is indeed created, and then interact with it to test the result?)
#!/usr/bin/env Python3
import unittest
import temp2
class Test1(unittest.TestCase):
@classmethod
def setUpClass(self):
self.w = temp2.Example()
def testHappy(self):
for i in [0,1,5]:
self.w.counter_fld.setText(str(i))
self.w.btn.click()
value = self.w.field.text()
self.assertEqual(value, str(i * 100))
def testSad(self):
for i in ["A", "foo"]:
self.w.counter_fld.setText(str(i))
self.w.btn.click()
# now what?
if __name__ == "__main__":
unittest.main()
(I'm using PyQt5 in Python3.6 on Windows.)
python pyqt5 python-unittest gui-testing
add a comment |
I have a parent widget that in some cases calls a custom QDialog to get user input. How do I write a unit test to ensure the dialog is called, and that it will handle correct input correctly?
Here's a mini example:
from PyQt5.QtWidgets import QDialog, QVBoxLayout, QWidget, QLabel, QApplication
from PyQt5.Qt import pyqtSignal, QPushButton, pyqtSlot, QLineEdit
import sys
class PopupDialog(QDialog):
result = pyqtSignal(str)
def __init__(self):
super().__init__()
layout = QVBoxLayout(self)
self.setLayout(layout)
lbl = QLabel("That's not a full number! Try again?")
layout.addWidget(lbl)
self.field = QLineEdit(self)
layout.addWidget(self.field)
self.btn = QPushButton("Ok")
self.btn.clicked.connect(self.on_clicked)
layout.addWidget(self.btn)
def on_clicked(self):
value = self.field.text().strip()
self.result.emit(value)
self.close()
class Example(QWidget):
def __init__(self):
super().__init__()
self.init_UI()
def init_UI(self):
layout = QVBoxLayout()
self.setLayout(layout)
lbl = QLabel("Please provide a full number")
layout.addWidget(lbl)
self.counter_fld = QLineEdit(self)
self.counter_fld.setText("1")
layout.addWidget(self.counter_fld)
self.btn = QPushButton("start")
layout.addWidget(self.btn)
self.btn.clicked.connect(self.on_clicked)
self.field = QLabel()
layout.addWidget(self.field)
self.show()
@pyqtSlot()
def on_clicked(self):
txt = self.counter_fld.text()
self.dialog = None
try:
result = int(txt) * 100
self.field.setText(str(result))
except ValueError:
self.dialog = PopupDialog()
self.dialog.result.connect(self.catch_dialog_output)
self.dialog.exec_()
@pyqtSlot(str)
def catch_dialog_output(self, value):
self.counter_fld.setText(value)
self.on_clicked()
def main():
app = QApplication(sys.argv)
ex = Example()
ex.show()
sys.exit(app.exec_())
if __name__ == '__main__':
main()
So in this case, I'd want to write a unit test that inserts different values into self.field and then tests that it works without PopupDialog for integers but that the PopupDialog is called when inserting a string.
(I know I could just test the functionality without the dialog, and that for this problem, the QDialog is not actually needed. I just tried to keep the example simple. Baseline is: I can get the unit test through the steps until the popup dialog is created, but how can I then test that it is indeed created, and then interact with it to test the result?)
#!/usr/bin/env Python3
import unittest
import temp2
class Test1(unittest.TestCase):
@classmethod
def setUpClass(self):
self.w = temp2.Example()
def testHappy(self):
for i in [0,1,5]:
self.w.counter_fld.setText(str(i))
self.w.btn.click()
value = self.w.field.text()
self.assertEqual(value, str(i * 100))
def testSad(self):
for i in ["A", "foo"]:
self.w.counter_fld.setText(str(i))
self.w.btn.click()
# now what?
if __name__ == "__main__":
unittest.main()
(I'm using PyQt5 in Python3.6 on Windows.)
python pyqt5 python-unittest gui-testing
Anything I can do/add/explain to get any answer at all?
– CodingCat
Mar 15 at 14:40
add a comment |
I have a parent widget that in some cases calls a custom QDialog to get user input. How do I write a unit test to ensure the dialog is called, and that it will handle correct input correctly?
Here's a mini example:
from PyQt5.QtWidgets import QDialog, QVBoxLayout, QWidget, QLabel, QApplication
from PyQt5.Qt import pyqtSignal, QPushButton, pyqtSlot, QLineEdit
import sys
class PopupDialog(QDialog):
result = pyqtSignal(str)
def __init__(self):
super().__init__()
layout = QVBoxLayout(self)
self.setLayout(layout)
lbl = QLabel("That's not a full number! Try again?")
layout.addWidget(lbl)
self.field = QLineEdit(self)
layout.addWidget(self.field)
self.btn = QPushButton("Ok")
self.btn.clicked.connect(self.on_clicked)
layout.addWidget(self.btn)
def on_clicked(self):
value = self.field.text().strip()
self.result.emit(value)
self.close()
class Example(QWidget):
def __init__(self):
super().__init__()
self.init_UI()
def init_UI(self):
layout = QVBoxLayout()
self.setLayout(layout)
lbl = QLabel("Please provide a full number")
layout.addWidget(lbl)
self.counter_fld = QLineEdit(self)
self.counter_fld.setText("1")
layout.addWidget(self.counter_fld)
self.btn = QPushButton("start")
layout.addWidget(self.btn)
self.btn.clicked.connect(self.on_clicked)
self.field = QLabel()
layout.addWidget(self.field)
self.show()
@pyqtSlot()
def on_clicked(self):
txt = self.counter_fld.text()
self.dialog = None
try:
result = int(txt) * 100
self.field.setText(str(result))
except ValueError:
self.dialog = PopupDialog()
self.dialog.result.connect(self.catch_dialog_output)
self.dialog.exec_()
@pyqtSlot(str)
def catch_dialog_output(self, value):
self.counter_fld.setText(value)
self.on_clicked()
def main():
app = QApplication(sys.argv)
ex = Example()
ex.show()
sys.exit(app.exec_())
if __name__ == '__main__':
main()
So in this case, I'd want to write a unit test that inserts different values into self.field and then tests that it works without PopupDialog for integers but that the PopupDialog is called when inserting a string.
(I know I could just test the functionality without the dialog, and that for this problem, the QDialog is not actually needed. I just tried to keep the example simple. Baseline is: I can get the unit test through the steps until the popup dialog is created, but how can I then test that it is indeed created, and then interact with it to test the result?)
#!/usr/bin/env Python3
import unittest
import temp2
class Test1(unittest.TestCase):
@classmethod
def setUpClass(self):
self.w = temp2.Example()
def testHappy(self):
for i in [0,1,5]:
self.w.counter_fld.setText(str(i))
self.w.btn.click()
value = self.w.field.text()
self.assertEqual(value, str(i * 100))
def testSad(self):
for i in ["A", "foo"]:
self.w.counter_fld.setText(str(i))
self.w.btn.click()
# now what?
if __name__ == "__main__":
unittest.main()
(I'm using PyQt5 in Python3.6 on Windows.)
python pyqt5 python-unittest gui-testing
I have a parent widget that in some cases calls a custom QDialog to get user input. How do I write a unit test to ensure the dialog is called, and that it will handle correct input correctly?
Here's a mini example:
from PyQt5.QtWidgets import QDialog, QVBoxLayout, QWidget, QLabel, QApplication
from PyQt5.Qt import pyqtSignal, QPushButton, pyqtSlot, QLineEdit
import sys
class PopupDialog(QDialog):
result = pyqtSignal(str)
def __init__(self):
super().__init__()
layout = QVBoxLayout(self)
self.setLayout(layout)
lbl = QLabel("That's not a full number! Try again?")
layout.addWidget(lbl)
self.field = QLineEdit(self)
layout.addWidget(self.field)
self.btn = QPushButton("Ok")
self.btn.clicked.connect(self.on_clicked)
layout.addWidget(self.btn)
def on_clicked(self):
value = self.field.text().strip()
self.result.emit(value)
self.close()
class Example(QWidget):
def __init__(self):
super().__init__()
self.init_UI()
def init_UI(self):
layout = QVBoxLayout()
self.setLayout(layout)
lbl = QLabel("Please provide a full number")
layout.addWidget(lbl)
self.counter_fld = QLineEdit(self)
self.counter_fld.setText("1")
layout.addWidget(self.counter_fld)
self.btn = QPushButton("start")
layout.addWidget(self.btn)
self.btn.clicked.connect(self.on_clicked)
self.field = QLabel()
layout.addWidget(self.field)
self.show()
@pyqtSlot()
def on_clicked(self):
txt = self.counter_fld.text()
self.dialog = None
try:
result = int(txt) * 100
self.field.setText(str(result))
except ValueError:
self.dialog = PopupDialog()
self.dialog.result.connect(self.catch_dialog_output)
self.dialog.exec_()
@pyqtSlot(str)
def catch_dialog_output(self, value):
self.counter_fld.setText(value)
self.on_clicked()
def main():
app = QApplication(sys.argv)
ex = Example()
ex.show()
sys.exit(app.exec_())
if __name__ == '__main__':
main()
So in this case, I'd want to write a unit test that inserts different values into self.field and then tests that it works without PopupDialog for integers but that the PopupDialog is called when inserting a string.
(I know I could just test the functionality without the dialog, and that for this problem, the QDialog is not actually needed. I just tried to keep the example simple. Baseline is: I can get the unit test through the steps until the popup dialog is created, but how can I then test that it is indeed created, and then interact with it to test the result?)
#!/usr/bin/env Python3
import unittest
import temp2
class Test1(unittest.TestCase):
@classmethod
def setUpClass(self):
self.w = temp2.Example()
def testHappy(self):
for i in [0,1,5]:
self.w.counter_fld.setText(str(i))
self.w.btn.click()
value = self.w.field.text()
self.assertEqual(value, str(i * 100))
def testSad(self):
for i in ["A", "foo"]:
self.w.counter_fld.setText(str(i))
self.w.btn.click()
# now what?
if __name__ == "__main__":
unittest.main()
(I'm using PyQt5 in Python3.6 on Windows.)
python pyqt5 python-unittest gui-testing
python pyqt5 python-unittest gui-testing
edited Mar 14 at 23:00
Backrub32
373322
373322
asked Mar 8 at 13:16
CodingCatCodingCat
2,32352638
2,32352638
Anything I can do/add/explain to get any answer at all?
– CodingCat
Mar 15 at 14:40
add a comment |
Anything I can do/add/explain to get any answer at all?
– CodingCat
Mar 15 at 14:40
Anything I can do/add/explain to get any answer at all?
– CodingCat
Mar 15 at 14:40
Anything I can do/add/explain to get any answer at all?
– CodingCat
Mar 15 at 14:40
add a comment |
1 Answer
1
active
oldest
votes
Well there are few ways to check if the QDialog is created,
1) patch the PopupDialog and verify if it was called.
from unittest.mock import patch
@patch("temp2.PopupDialog")
def testPopupDialog(self, mock_dialog):
self.w.counter_fld.setText(str("A"))
self.w.btn.click()
mock_dialog.assert_called_once()
2) To interact with the PopupDialog you may have to do a bit more.
def testPopupDialogInteraction(self):
self.w.counter_fld.setText(str("A"))
self.w.btn.click()
if hasattr(self.w.dialog, "field"):
self.w.dialog.field.setText(str(1))
self.w.dialog.btn.click()
value = self.w.field.text()
self.assertEqual(value, str(1 * 100))
raise Exception("dialog not created")
On a different note, there is a better way to verify the user input i.e QRegExpValidator. Check this SO answer
In the present method, it will continue creating a Popup everytime a user inputs improper value and would create a poor user-experience(UX). Even websites use validators instead of Popups.
Thanks for the pointer to mock and @patch, this was what I was looking for! (And yes, I know the popup in this case makes no sense. My actual popup asks for user choices and is far more complex, both the popup and the circumstances where it is called. I just wanted to create a very quick MVE for this.)
– CodingCat
Mar 18 at 14:54
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55064026%2fpyqt-unit-test-that-qdialog-is-created%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Well there are few ways to check if the QDialog is created,
1) patch the PopupDialog and verify if it was called.
from unittest.mock import patch
@patch("temp2.PopupDialog")
def testPopupDialog(self, mock_dialog):
self.w.counter_fld.setText(str("A"))
self.w.btn.click()
mock_dialog.assert_called_once()
2) To interact with the PopupDialog you may have to do a bit more.
def testPopupDialogInteraction(self):
self.w.counter_fld.setText(str("A"))
self.w.btn.click()
if hasattr(self.w.dialog, "field"):
self.w.dialog.field.setText(str(1))
self.w.dialog.btn.click()
value = self.w.field.text()
self.assertEqual(value, str(1 * 100))
raise Exception("dialog not created")
On a different note, there is a better way to verify the user input i.e QRegExpValidator. Check this SO answer
In the present method, it will continue creating a Popup everytime a user inputs improper value and would create a poor user-experience(UX). Even websites use validators instead of Popups.
Thanks for the pointer to mock and @patch, this was what I was looking for! (And yes, I know the popup in this case makes no sense. My actual popup asks for user choices and is far more complex, both the popup and the circumstances where it is called. I just wanted to create a very quick MVE for this.)
– CodingCat
Mar 18 at 14:54
add a comment |
Well there are few ways to check if the QDialog is created,
1) patch the PopupDialog and verify if it was called.
from unittest.mock import patch
@patch("temp2.PopupDialog")
def testPopupDialog(self, mock_dialog):
self.w.counter_fld.setText(str("A"))
self.w.btn.click()
mock_dialog.assert_called_once()
2) To interact with the PopupDialog you may have to do a bit more.
def testPopupDialogInteraction(self):
self.w.counter_fld.setText(str("A"))
self.w.btn.click()
if hasattr(self.w.dialog, "field"):
self.w.dialog.field.setText(str(1))
self.w.dialog.btn.click()
value = self.w.field.text()
self.assertEqual(value, str(1 * 100))
raise Exception("dialog not created")
On a different note, there is a better way to verify the user input i.e QRegExpValidator. Check this SO answer
In the present method, it will continue creating a Popup everytime a user inputs improper value and would create a poor user-experience(UX). Even websites use validators instead of Popups.
Thanks for the pointer to mock and @patch, this was what I was looking for! (And yes, I know the popup in this case makes no sense. My actual popup asks for user choices and is far more complex, both the popup and the circumstances where it is called. I just wanted to create a very quick MVE for this.)
– CodingCat
Mar 18 at 14:54
add a comment |
Well there are few ways to check if the QDialog is created,
1) patch the PopupDialog and verify if it was called.
from unittest.mock import patch
@patch("temp2.PopupDialog")
def testPopupDialog(self, mock_dialog):
self.w.counter_fld.setText(str("A"))
self.w.btn.click()
mock_dialog.assert_called_once()
2) To interact with the PopupDialog you may have to do a bit more.
def testPopupDialogInteraction(self):
self.w.counter_fld.setText(str("A"))
self.w.btn.click()
if hasattr(self.w.dialog, "field"):
self.w.dialog.field.setText(str(1))
self.w.dialog.btn.click()
value = self.w.field.text()
self.assertEqual(value, str(1 * 100))
raise Exception("dialog not created")
On a different note, there is a better way to verify the user input i.e QRegExpValidator. Check this SO answer
In the present method, it will continue creating a Popup everytime a user inputs improper value and would create a poor user-experience(UX). Even websites use validators instead of Popups.
Well there are few ways to check if the QDialog is created,
1) patch the PopupDialog and verify if it was called.
from unittest.mock import patch
@patch("temp2.PopupDialog")
def testPopupDialog(self, mock_dialog):
self.w.counter_fld.setText(str("A"))
self.w.btn.click()
mock_dialog.assert_called_once()
2) To interact with the PopupDialog you may have to do a bit more.
def testPopupDialogInteraction(self):
self.w.counter_fld.setText(str("A"))
self.w.btn.click()
if hasattr(self.w.dialog, "field"):
self.w.dialog.field.setText(str(1))
self.w.dialog.btn.click()
value = self.w.field.text()
self.assertEqual(value, str(1 * 100))
raise Exception("dialog not created")
On a different note, there is a better way to verify the user input i.e QRegExpValidator. Check this SO answer
In the present method, it will continue creating a Popup everytime a user inputs improper value and would create a poor user-experience(UX). Even websites use validators instead of Popups.
edited Mar 18 at 11:31
answered Mar 18 at 11:05
Ja8zyjitsJa8zyjits
881821
881821
Thanks for the pointer to mock and @patch, this was what I was looking for! (And yes, I know the popup in this case makes no sense. My actual popup asks for user choices and is far more complex, both the popup and the circumstances where it is called. I just wanted to create a very quick MVE for this.)
– CodingCat
Mar 18 at 14:54
add a comment |
Thanks for the pointer to mock and @patch, this was what I was looking for! (And yes, I know the popup in this case makes no sense. My actual popup asks for user choices and is far more complex, both the popup and the circumstances where it is called. I just wanted to create a very quick MVE for this.)
– CodingCat
Mar 18 at 14:54
Thanks for the pointer to mock and @patch, this was what I was looking for! (And yes, I know the popup in this case makes no sense. My actual popup asks for user choices and is far more complex, both the popup and the circumstances where it is called. I just wanted to create a very quick MVE for this.)
– CodingCat
Mar 18 at 14:54
Thanks for the pointer to mock and @patch, this was what I was looking for! (And yes, I know the popup in this case makes no sense. My actual popup asks for user choices and is far more complex, both the popup and the circumstances where it is called. I just wanted to create a very quick MVE for this.)
– CodingCat
Mar 18 at 14:54
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55064026%2fpyqt-unit-test-that-qdialog-is-created%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Anything I can do/add/explain to get any answer at all?
– CodingCat
Mar 15 at 14:40