Skip to main content

Test Cases

Test cases is the document that contains the information regarding the Test data, Prerequisite, Expected result etc. These test cases developer by the QA Team before develop the code. After develop the code , QA team verified these test cases with the execution of code and as per the output match that with expected result and provide the status of that test Pass or Fail.

Test Case document include all possible Test cases by understand the Requirement Document, Design Document. Only your test cases will define the quality of the software. if Test cases include all possible scenario then it is easy to test the application and find bugs and provide good quality of the Software.
Following fields are required for the Test Cases


  • Test Case id: This the Test Cases id for the specific test case for future reference. This is the Unique Id
  • Test Case Description/Objective: It include the description regarding your Test. Suppose you are writing the Test cases of Login Page then then it is include like "To Verify the Login Form".
  • Tester: It include the Tester Name
  • Environment: It include the environment that we are using for Testing . Suppose we are using Window/Linux/Mac operating system with, 1GB Ram, 80 GB Hard Disk, Firefox/Chrome/Opera/Safari browser etc.
  • Version: It include the version of release. 
  • Module: It include the module name. 
  • Prerequisite: it include the prerequisite condition that should be fulfilled before execution of the Test. For Login form it may be Login form should be developed, It include both email/username field and Password field with a Submit button.
  • Date of Creation: It include the Date of writing Test case.
  • Date of Release: It include the date of releasing the software or that module.
  • Test Steps: It include the procedure that we are following to execute the test. In case of Login form, it is like put valid username and valid password and click on Submit button.
  • Test Data: It include the data that will used to as a input for test. 
  • Expected Result: It include the result which is expected as per the requirement document. 
  • Actual Result: It include the result which will be generated after execution of the code. 
  • Status: It include the status Pass or Fail. If Actual result match the expected result then status is Pass otherwise status is Failed. 
  • Date: It include the date of execution.
  • Comments: If Tester/developer have any double or he/she want to write any message then he/she can use this comment section. 
  • Defect Id/Link: It include a link for Fail test cases with the defect report. 
  • Test Type: It include the type of test that needed. it may be Function Test, Regression Test, Performance Test.
  • Requirements: It include the requirement as per the Test cases with exact section number for better understanding.
  • Attachment: It include any attachment for reference for explain the other team member.
  • Automation: It include the information that the test case will execute manually or by automation. 
Download the format of the Test case template 


Comments

Popular posts from this blog

Why Jmeter is best option for Performance Testing?

There are multiple tools in market for performance testing of any software but Jmeter is the best solution among all of them due to some reason listed below 1) Jmeter is the open source application so users who use this application will not to pay anything. 2) You can use Jmeter for performance of any web application,  Databases and Web Services (REST and SOAP APIs). 3) Jmeter have the user friendly UI component so it is very easy to use. 4) Jmeter can be used to simulate to put maximum number of concurrent users on a server, network or object to test its strength or to analyze overall performance under different load types. 5) Jmeter also use for functional testing for static( JavaScript and HTML) and dynamic( JSP, Servlets and AJAX) resources. 6) Jmeter provides Verity of graphical representations for performance report so it is easy to understand.

How You Can Test Database?

Now we know the Database Testing which you can learn in my last article. In this article we will discuss about the steps that need to following to test any Database. Database Tester should have some basic knowledge regarding SQL Command like DDL (create/drop),  DML (Insert/Delete/Update) and DCL (Grant/Revoke).

Causes of Software Defects

It is practically impossible that developer develop a bug free software and that software we can deliver without Testing. If the complexity of the software increased then there must be bugs that can harm the users who will use that software.