Basics-Test Case Writing

-By Madhavan Karthikeyan

• Functionality Testing• Performance Testing• Usability Testing• Server Side Interface• Client Side Compatibility• Security

2

In General a test case basically is a brief statement of something that should be tested

“As set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.” (IEEE)

3

The basic objective of writing test cases is to validate the testing coverage of the application.

So writing test cases brings some sort of standardization and minimizes the ad-doc approach of testing.

4

Find defects Maximize bug count Block premature product releases Help managers make ship / no-ship

decisions Assess conformance to specification Conform to regulations Verify correctness of the product Assure quality

5

Read Specification and Requirement Carefully

Be clear with the design and implementation details

Analyze and Identify all possible scenarios Identify the test environments and test

types Should be clear of behavior under failure

condition (invalid input, boundary values etc)

6

Short› Tests should be very short (a paragraph or

so) Cross-Platform

› Test should be as cross-platform as reasonably possible, working across different devices, screen resolutions, paper sizes, etc.

Note: Properly written test cases helps both Testers as well as Developers while execution and debugging.

7

The test case for different module should be mentioned in a a single worksheet in a single file.

The name of the excel file should be TypeofTesting_ModuleName

Module names should be in Capitals and Bold. Screen Names should be bold and have camel

notation ie., the first word in capital letters and rest all in small letters.

All the objects like textbox, listbox, Checkbox, radio buttons etc should be in italics and bold

The link names should be mentioned in Italics, bold and underline below the work e.g., ‘Sign Out’ link should be mentioned as ‘Sign Out’

8

Test Case Id – Must be unique across the application

Test Case description – The test case description must be very brief

Test Case Priority – Priority of the test case

Test Case Type – To identify the type of test case

Precondition – What should be present in the system, before the test can be executed

9

Testing the functionality of the web sites the following should be tested:

› Server Side Interface:In web testing the server side interface should be tested. This is done by verify that communication is done properly. Compatibility of server with software, hardware, network and database should be tested.

10

Testing the functionality of the web sites the following should be tested:

› Client Side Compatibility:The client side compatibility is also tested in various platforms, using various browsers etc.

› Security: The primary reason for testing the security of a web is to identify potential vulnerabilities and subsequently repair them.• Network Scanning• Vulnerability Scanning• Password Cracking• Log Review• Integrity Checkers• Virus Detection

11