After completion of test planning and required training to testing team, corresponding testing team members will prepare list of test cases for their responsible modules. There are four types of test case design methods to cover core level testing (Usability & Functionality testing).
1.User interface base test case design (GUI test cases) Development can make sure that during development they follow the guidelines and prototype to build an application and as a test engineer it is our responsibility to validate the product/application against GUI standards followed by our organization or by viewing screens and project standards. Most of test Engineers combined GUI test cases as part of functional test case design but some engineers write GUI test cases depends on organization user interface conventions or project standards.
2.Input Domain based test case design (Field Level test cases)
In general test engineer write test cases based on user case/ functional spec understanding. These use cases /functional spec provides field level info such as mandatory, read-only, data type, field size, minimum & maximum value, validation, message type etc. If you do not get field level validation sheet along with use case document, insist your lead/manager to get the same. Here I will share sample excel document contain most important columns at field level.
3.Interface level based test case design (Functional test cases)
Interface test cases (call as functional) will be prepared based on business requirements, functional specification or Use cases. These test cases cover the functionality of individual actions or buttons. Each time tester design the steps for action differently, so due to this he/she requires lot of effort to design and test steps won’t be consistent.
We have made common test case template, in this you need to do minimal changes to design test cases for each action at interface level. In this template has description, steps and expected results are consistent.
4.Business logic based test case design (Integration and End to End test cases)
Many test engineers define integration and end to end test cases based on their clear understanding on several use cases for the respective module and end customer point of view. None of the engineers use any technique to define these test cases and project 100% test coverage is done.
What we suggest here, prepare flow diagram from your understanding, review the same with the person who prepared use cases. Once it is reviewed, apply Cyclomatic Complexity method to directly measure linear dependent path through the flow diagram. This technique ensures that all overall process flows are identified and right information is passed between modules. Each path consider as one end to end test case. Pl. refer Cyclomatic Complexity method.
Basic elements can be used to prepare a flow chart (Diagram designer is a open source tool having such features to design flow diagrams)
Squares, diamonds and arrows form a flow chart. Squares represent tasks, while diamonds represent decisions, and arrows represent the direction of information.