You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 29, 2018. It is now read-only.
Usability Enhancements and defects to Selenium IDE regarding test suite and test case
creation.
What steps will reproduce the problem?
--Consider following the seemingly basic steps--
1. open Selenium IDE
2. create new test suite TS_A
3. create 2 new test cases with token content and save them as TC_A and TC_B
4. add test case TC_B to the new test suite TS_A
5. select test suite TS_A and click 'save test suite'
6. select test suite dialog window opens ???
7. select TS_A and click the save btn
8. TC_A incorrectly appears added to suite TS_A (see step 4 above)
PROBLEMS:
a) test suite creation process should always prompt user for a name. This means that
'save test suite' and 'save test suite as' end up doing the same thing.
b) saving test suite brings up 'save test suite' dialog again!
c) adding test case to test suite at step 4. above now shows 2 copies. Not clear what
test case belongs to what test suite when they are listed sequentially in 'Test Case'
section without indentation.
d) see step 6 above. Why are we being asked to select the suite AGAIN?
e) see step 8 above.
Selenium version: 2.8.0
OS: Windows 7 Home
Browser: Firefox
Browser version: 35.0
Please provide any additional information below. A sample reduced test
case, or a public URL that demonstrates the problem will intrigue our merry
band of Open Source developers far more than nothing at all: they'll be far
more likely to look at your problem if you make it easy for them!
Originally reported on Google Code with ID 8422
Reported by
ToddAJStewart
on 2015-01-23 00:56:19- _Attachment: Selenium.PNG
![Selenium.PNG](https://storage.googleapis.com/google-code-attachments/selenium/issue-8422/comment-0/Selenium.PNG)_
The text was updated successfully, but these errors were encountered: