| Re: [swtbot-dev] Testing simple SWT Dialogs |
|
Hi Patrick, Thanks for your answer! But somehow Display.asyncExec is not called at all in my test. The syncExec is calling my MessageDialog fine. But than the test is waiting for the Dialog to be closed. My code locks like that now:
@Test
public
void testInfoDialogWithDontShowAgain()
{ Display.getDefault().asyncExec(() -> { System.out.println("Hallooooo"); MessageDialog.openConfirm(new
Shell(Display.getDefault()), "A
MessageDialog",
"Buhu"); }); SWTBotPreferences.PLAYBACK_DELAY
= 100; SWTBot
bot =
new SWTBot();
bot.button("OK").click(); } Could you give me an example to open this MessageDialog and close it with SWTBot by clicking the OK Button? Thanks very much Stefan Von: swtbot-dev-bounces@xxxxxxxxxxx <swtbot-dev-bounces@xxxxxxxxxxx>
Im Auftrag von Patrick Tasse Hi Stefan, The short answer is that the Shell you create to feed to the SWTBot instance has not been opened, so there is no active shell which makes activeShell() fail. Long answer: Usually we use SWTBot to test an existing application. Here the test is both creating the application and testing it. I guess it is OK for trying out SWTBot. However you probably should create your application (the Dialog under test) using purely SWT APIs, not using SWTBot APIs (for example you can use Display.getDefault().asyncExec(...) directly). Then use SWTBot APIs to test the dialog. I would try to avoid using activeShell() as much as possible. Lately we notice problems where opened shells do not become active, due to the platform or the window manager, I'm not sure. But it's usually better to get a shell by name and
activate it manually, like you do at the end of the test. It's usually not necessary to add sleeps in the tests, most SWTBot finder methods like shell(...) or button(...) have a retry with timeout mechanism, so if the searched widget comes only after a short delay, it still works. Not activeShell()
though, it tries only once and fails immediately... Hope this helps, Patrick On Thu, Sep 20, 2018 at 8:52 AM Stefan Nöbauer <stefan.noebauer@xxxxxxxxxxxxxxxxxx> wrote:
|