-
Notifications
You must be signed in to change notification settings - Fork 0
Testing Script
Denis Bogdanas edited this page Oct 12, 2015
·
9 revisions
Test Area | Test | Expected Results |
---|---|---|
General Plugin | Load Plugin | Status icon in the lower right visible |
Standard Launch Listener | run a standard launch | REST Post to server. |
Debug Launch Listener | run a debug launch | REST Post to server. |
Test Launch Listener | launch all tests | REST Post to server. |
Test Launch Listener | launch single test | REST Post to server. |
User Tagged Data | launch any test | REST data should include username |
Go to settings -> Other Settings -> COPE
- The default URL should be visible.
Reset functionality:
- Change something in the textboxes. Click reset. Values should revert to the initial state.
- Trigger a REST event. Result: REST post to the initial URL.
Apply functionality:
- Change the URL. Click apply.
- Go to settings again. New value should be stored.
- Trigger a REST event. Result: REST post to the new URL.
Test button:
- Set a valid URL. Press "Test". Result: popup "Connection Successful" with the status code. Right now it is successful any time the connection could be established, regardless of the status code.
- Set an URL containing a closed port. Press "Test". Result: popup "Connection failure".
- Set an URL containing as port a large number. Press "Test". Result: "Invalid URL".
- Set as URL "http://". Press "Test". Result: Result: "Invalid URL".
- Set as URL a stream of alphanumeric characters. Press "Test". Result: "Connection failure".
- Test 1
- create a long JUnit test, for example calling Thread.wait(5 sec)
- COPE settings -> change the URL to one that will get stuck for some seconds, for example put an unused port
- run the JUnit test
- keep clicking on the screen while the task is running -> the screen is responsive.
- keep clicking on the screen after all tests passed. -> the screen is also responsive. It wasn't like this before.
- check the plugin DEV IDE log -> after some seconds the ConnectionException will be logged
2.. Test 2. The same scenario for running a program.