| Re: [tigerstripe-dev] GUI JUnit testing |
Jim,
this looks like a good start :-)
I think you need to be sure that you have references between the artifacts you create. I'd put this right at the top of the list. (It's different fro your Todo Item of moving attributes etc.)
Associations/Dependencies will be naturally tested - you just need to be sure that you do the right checks, but you should add Inheritance (moving a parent, moving a child), Implements (which doesn't work properly today :-( ) and references - eg attributes of a given datatype, methods of a given return type and so on. This is where we have had some issues in the past.....
Other than that I look forward to seeing the results :-)
Rich
From: tigerstripe-dev-bounces@xxxxxxxxxxx [mailto:tigerstripe-dev-bounces@xxxxxxxxxxx] On Behalf Of Jim Strawn (jistrawn)
Sent: 03 July 2008 03:07
To: Tigerstripe developers list
Subject: [tigerstripe-dev] GUI JUnit testing
Here is a first stab at a test plan for the Tigerstripe Explorer. I expect that I will add more use cases as I spend more time with the UI. If there are any cases that you can think to add (or you would think I should remove) please let me know. I will plan to start implementing this plan, and add diagrams testing as I get more familiar with the WindowsTesterPro.
http://wiki.eclipse.org/Explorer_Test_Plan (it is hanging off of the http://wiki.eclipse.org/TigerstripeF2F_20080616 page).
Thanks,
Jim
_______________________________________________
tigerstripe-dev mailing list
tigerstripe-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tigerstripe-dev