test case generation with white box approach
i'm planning to generate test cases from UML diagrams from design and implementation phase, I myself think of class diagram and source code, i'be be thankful if some one guide me if i could something better than them?
One problem about UML diagrams or mid to low level engineering specs is it focuses more on how the software works, vs. what the software is suppose to work. For test cases, the requirements is your best bet for functional test cases.
Class diagrams are useful for thinking of ideas around input validations. For example, identifying say string to int, int to string, date objects or day/month/year, where data is being parsed and processed.
I think in terms of end to end level test cases, the sequence and architectural diagrams are most useful.
Sequence diagrams will help you understand the data flow, and you can come up with scenarios that match the sequence, or think of scenarios that might one off a particular sequence of events. For example, finding edge cases where a particular sequence is not enforced but allows you to perform actions out of sequence. For example, say you have a post login 3 step process, say you login, do step 1 and step 2, then log out, then force step 3.
Probably the most useful out of UML diagrams is architectural diagrams. This will allow you to say review a change happening to the system, and see how it impacts your software environment. For example, say a queue processor is upgraded on one of the systems, how will this impact the functionality of the other systems that use it?
Recently explored a tool which helps in generating test case as the tools has many solutions. Each solutions takes minimal inputs and automatically generate testcases. Also provides an ability to modify test cases when scope changes. testgleam