Aboo S

Test Cases are the implementation of a test case design which will help the software tester to detect defects in the application or the system being tested. This should be the primary goal of any test case or set of test cases. When I write a test case, I think of both types of test cases, positive test cases and negative test cases. Positive test cases are those which execute the happy path in the application and make sure that the happy path is working fine. Negative test cases as the name suggests are destructive test cases which are documented with some out-of-box thinking to break the system.
A Test Case should be documented in a manner that is useful for the current test cycle and any future test cycles. At a bare minimum each test case should contain: Sr No, Summary or Title, Description, Steps to reproduce, Expected Results, Actual Results and Status of the test case or remarks.

Read More...

Main purpose of testing is to detect defects / bugs in the application before it is released into production; furthermore defects are only product the testing team produces that is seen by the project team. So document the defects in a way that is useful in the defect remediation process - at a bare minimum each defect should contain: Summary, Description, Priority, Severity, Impacted Area, How to reproduce the defect and Current Status of defect.

Read more...