Question { TCS, 10228 }

what are the inputs fo writing testcases and what are the
outputs after executing the testcases?

Answer

You should be basing several things while you go about documenting your test cases:

1) Your Use Cases should form a strong base for you to understand several exception flows. However, this can only be achieved if you have a strong Business Analyst with greater depths of domain knowledge.
2) You should base your test scenarios and cases on the real-time business scenarios. For instance, you should be able to think negatively and start to think framing your questions surrounding...the "What if...you do x....does it result in y (Pass condition) or is it resulting in z (Fail condition)
3) Bring your intuition and trust your conscious senses about how the user might about making an entry into the system while working with the end system
4) Start having a bird's eye view of the application. Understand the vision why application is currently being devised
5) Once you write your test cases, you should be able to provide them to a user who has not worked with the system earlier to proceed on with the execution. Tester should ensure that he has documented all the alternate flows, presence of test data, any configuration requirements for the test case to be either passed or failed
6) Performance of the screens and the screen activity needs to be taken into account. User should not be sight any kind of system freezes or he should ensure that the system does not die on him when he is interacting with the system
7) The user navigation flow should be consistent, if the system uses any kind of keyboard strokes
8) User should see that the actions provided on one particular screen should not sway away from the actions present on a consecutive screen. Consistency with respect to the usability of the screens and the placements should be taken into consideration while developing the screens by the developers
9) What is expected and How you can reach the expected are the two primary things that one has to look out for from a test case
10) Most importantly, your test cases should be maintainable in the long run saying that if you are writing Manual test cases today, there should not be any redundant test cases and your test cases should be used as the base to automate or build an automation test suite in the future when your enterprise or application vendor or Independent Software Vendor decides to do so.