TestingGeek

This application allows software engineers to model and design their software in terms of UML (Universal Modeling Language). It also gives functionality of generating code from the software design and keeping code and model in synchronization. Testing this desktop application is quite a big challenge in itself because of the complexities involved.

 Application Summary
Design and modeling tools are used by the software engineers and architects to design the software system. Using these tools you can design at the high level system using use case diagrams or at the deepest level in terms of interaction diagram and collaboration diagram.  These tool also gives functionality of generating source code from the class diagram. Generated code and class diagram can remain in sync, and any changes made in the source code will be reflected in the model as well. 
Apart from generating code from the model, models can be generated from the existing source as well. The process of generating model from the source code is known as reverse engineering or visualization.

• Tool might not work properly with different type of diagram

Test cases should be present for all the supported UML diagrams and elements
• UML models for systems in actual scenario could be big

Test the system with big UML diagrams and all the UML elements.
• Generated code might not be proper

Test the system will all supported diagram and generated code by them
• Changes made in the code will not be reflected in the system and model and code will not be in synch

Include test cases for making changes in the model/code and make sure that code and model are always in synch. 
• Tool might not work properly on various supported platforms

Include test cases for all the supported platforms.
• Tool might not work properly after Internationalization

Plan I18N Testing and translation verification testing well in advance
• Tool might not adhere to the accessibility environment

Plan accessibility testing and make sure that tool is accessibility compliant.

• Create two classes, classA and classB. Inherit classB from classA and generate code. Generate java code for these. In the generated code classB should be extending classA. Add some variable in the classB and this variable should be added in model as well
• Take three java files classA, classB and InterfaceC. ClassB should be extending classA and implementing InterfaceC. Visualize/Reverse engineer these files and make sure proper UML model is created to represent this code. Add some variable in the model and make sure that this gets added in the code as well

• Test case execution status

This was a simple tracking mechanism and it was tracked for number of test cases to be executed for every test cycle. Test cases were maintained in the Rational Test Manager, and execution was also tracked there
• Defect status

Defects were maintained in the Rational Clear Quest and every week how many defects were filed and what is the status of these defects were being analyzed. We were following the conventional defect cycle i.e Open -> Fixed -> Resolved -> Closed.
• Defect trend

It was a simple chart for the number of defects filed every week and was giving information on how product is being stabilized.