Test Cases for Triangles

We have studied the properties of various triangles in school. Let us apply those properties to test a triangle today.

A triangle is made of three sides (and three angles of course). Let us assume that the vertices are A, B and C, and corresponding sides are a, b, c.

Test cases follow:

1. Enter 0, a, b. No triangle is formed.
2. Enter 1, 2, 4. No triangle is formed because for a valid triangle a+b>c, b+c>a, c+a>b.
3. Enter angles A, B, C. The sum of the angles should be 180 degrees.
4. Enter a, a, a. Valid equilateral triangle.
5. Enter a, a, b. Valid isosceles triangle.
6. Enter angles A, B, C. If any of the angles is 90 degrees and the sum is 180 degrees, it is a right angle triangle.
7. Enter angles A, B, C as 90, 90, 0. The sum of angles is 180 degrees, still the triangle cannot be formed.
8. Enter negative value for a side, e.g. -1, -1, -1. Invalid input.
9. Enter character value for one of the sides, e.g. a, 2, 2. Invalid input.

Please add more to this.

Traceability Matrix: How to Map Requirements to Test Cases

Refer to following articles for more:

•  Traceability Matrix: How to Ensure the coverage of Requirements in Test Cases
•  FAQs about UAT (User Acceptance Testing)
•  Project Planning: How to Design the Project Flexibility Matrix
•  How to Develop a Software Change Management Process and Governance
•  How to Prepare Workflow Diagram and Systems

When you write test cases from a requirement document or use case document, you should remain sensitive towards the coverage of the requirement and converting them to testable items. The test cases are designed keeping in mind about the requirements coverage. If there are areas not covered in the test case, it will go untested. In order to verify whether all the requirements are being tested or not, Traceability Matrix is created. It maps requirements to the test cases.

How to Approach Test Estimation

Test estimation is not an easy task. Various schools of thoughts suggest varied strategies of estimation. A number of techniques are available for task estimation. Before we talk about any of the estimation technique, which is out of the scope of current post, we should talk about the activities that need to be kept in mind while estimating testing effort.

Majorly, the activities can be categorized under Test Planning, Requirement Analysis, Test Case writing and/ or scripting, Test Case/ Script execution, Training, Defect Reporting and Tracking, Regression and Retesting and, Reporting. Then we should incorporate following possibilities in the real life scenarios: possibility or parallelization of tasks, dependencies and roadblocks and, risks. Let us dig further into each of them.