welcome to XRM blog

Keep in touch with latest CRM/ERP articles

To remain competitive your organisation must be efficient across the business process spectrum. To do so you need to take sound decisions based on a balance between the cost and risk. To do so you will be heavily dependent on your content management in itself needs...

image
Blog

what is test case in software testing?

By Himanshu on 12/19/2022

What is Test Case

A test case is described as a set of scenarios under which a tester decides whether or not an application is operating in accordance with the needs of the customer. Preconditions, case name, input requirements, and anticipated outcome are all included in test case design. An activity at the first level, test cases are derived from test scenarios.
It is a comprehensive document that includes all relevant inputs (both positive and negative) as well as the navigational steps required for the test execution procedure. Writing test cases is an one-time activity that can be utilised for regression testing in the future.

How to create effective Test Cases:

• Observe the scope and requirements of the project (using SRS or BRS docs)
• Pay close attention to project updates.
• Consider yourself as being the end user.
• Try to divide the application into manageable sections and become well-versed in each
  area.
• Should take the negative and positive scenarios based on the project’s requirements
• Should have a good template having the basic columns in place as following below
  columns must exist in test case template -:
    Test case ID, Test Objective, Test Steps, Expected Result, Actual Result, Status

Tester should be ensured before execution of test cases:

• Test Cases should be unique, avoid irrelevant & duplicate test cases.
• Confirm that all test cases have covered all specified requirements mentioned in the
   specification document.
• Test cases should be transparent & straight-forward. 
• Test cases must be written in a format that makes it simple for other stakeholders to
   understand and make changes as needed.
• Don't take the system's features and functions for granted.
• Simple and concise descriptions are required.
• To reduce misunderstanding during execution, test case steps should be divided into
  the smallest possible units. 

Types of Test cases:

Unit Test Cases: To ensure that each component of the software operates as planned, unit testing examines individual software modules or components. The smallest measurable component of software is called a unit. A single output frequently requires several inputs.

Integration Test cases: To examine the interactions between the various software modules, an integration test case is created. This test case's primary goal is to validate that the interfaces between various modules function properly. Usually, the testing team will design integration test cases with assistance from the development team.

Data base Test Cases: This kind of test case tries to investigate internal processes, assisting testers in understanding where the data is moving in the system. SQL queries are widely used by testing teams to create database test cases.

Functional Test Cases: This kind of testing may show if the user interface of an app interacts well with the rest of the system and its users by determining whether the intended functions of the application are successfully completed or not. Functionality tests may be run without gaining access to the application's internal structures since they are based on user stories or system requirements. The QA team often creates this test scenario.

Performance Test Cases:  Performance test cases may be used to understand how the system will function in the actual world since they have a very stringent set of success requirements. The testing team normally develops performance test cases, however due to the high number of performance tests that one system may require, they are frequently automated. 

User Interface Test Cases: This kind of test case can confirm that a particular GUI component looks, and functions as intended. Grammar and spelling mistakes, broken links, and visual flaws can all be found in user interface (UI) components that the user interacts with. To make sure an app runs consistently across several browsers, UI tests frequently need cross-browser capabilities. With some assistance from the design team, the testing team often creates these test cases.

Security Test Cases: The system restricts activities and permissions as needed to secure data, and these test cases are used to verify this. Case studies for security tests often centre on authentication and encryption and involve security-based tests like penetration testing. If there is a security team in the company, they are in charge of creating these test cases.

Regression Test Cases: This test verifies that current system functionalities have not been impacted by recent code or programme modifications. Regression testing involves picking all or part of the previously ran test cases and rerunning them to make sure the software's current functions are still working as intended.

Benefits of Creating Test Cases:
Writing test cases ensures complete test coverage across the application, which helps the testing team be ready, additionally it also has an influence on quality assurance and the user experience. Early information that can be used to improve the quality of product will be uncovered with the help of test cases.

By the help of test cases, Tester can see defects, potential improvements & things that don’t quite make sense. These issues may be fixed before the application is made available for production use. Writing test cases enables any newly hired testers to quickly become familiar with the product without specialized training. After all, test cases describe in detail how to use the product and what may be expected from certain activities. 
 

Expected Results
how to write test case
Status
Test Objective
Testcase ID
Testing
Author
Blog Calendar
Blog Calendar List
2024 Apr  1  4
2024 Mar  19  4
2024 Feb  21  3
2024 Jan  6  7
2023 Dec  9  6
2023 Nov  28  5
2023 Oct  83  12
2023 Sep  191  9
2023 Aug  56  7
2023 Jul  31  5
2023 Jun  20  4
2023 May  43  5
2023 Apr  30  5
2023 Mar  90  6
2023 Feb  104  5
2023 Jan  37  4
2022 Dec  94  7
2022 Nov  248  2
2022 Sep  13  1
2022 Aug  27  2
2022 Jun  7  2
2022 May  3  2
2022 Apr  6  2
2022 Mar  1  1
2022 Feb  2  1
2022 Jan  1  1
2021 Dec  3  1
2021 Nov  2  1
2021 Oct  1  1
2021 Sep  11  1
2021 Aug  37  5
2021 Jul  36  4
2021 Jun  1202  5
2021 May  31  3
2021 Apr  1995  3
2021 Mar  188  5
2021 Feb  2078  7
2021 Jan  2962  9
2020 Dec  431  7
2020 Sep  73  3
2020 Aug  670  3
2020 Jul  125  1
2020 Jun  74  3
2020 Apr  68  3
2020 Mar  12  2
2020 Feb  27  5
2020 Jan  34  7
2019 Dec  17  4
2019 Nov  29  1
2019 Jan  23  2
2018 Dec  63  4
2018 Nov  68  3
2018 Oct  18  3
2018 Sep  1132  11
2018 Aug  7  2
2018 Jun  13  1
2018 Jan  68  2
2017 Sep  585  5
2017 Aug  17  1
2017 Jul  17  2
2017 Jun  62  2
2017 May  21  1
2017 Apr  35  2
2017 Mar  135  4
2017 Feb  773  4
2016 Dec  203  3
2016 Nov  822  8
2016 Oct  304  10
2016 Sep  697  6
2016 Aug  39  1
2016 Jun  1871  6
2016 May  110  3
2016 Jan  71  2
2015 Dec  465  6
2015 Nov  4  1
2015 Oct  13  1
2015 Sep  1464  6
2015 Aug  14  1
2015 Jul  128  2
2015 Jun  10  1
2015 May  20  1
2015 Apr  30  3
2015 Mar  80  3
2015 Jan  5334  4
2014 Dec  17  1
2014 Nov  2257  4
2014 Oct  68  1
2014 Sep  107  2
2014 Aug  5272  1
2014 Jul  48  2
2014 Apr  2578  12
2014 Mar  300  17
2014 Feb  220  6
2014 Jan  1510  16
2013 Dec  21  2
2013 Nov  688  2
2013 Oct  256  3
2013 Sep  11  1
2013 Aug  40  3
2013 Jul  214  1
2013 Apr  57  6
2013 Mar  2276  10
2013 Feb  127  3
2013 Jan  340  2
2012 Nov  57  2
2012 Oct  499  10
Tag Cloud
Interested in our services? Still not sure about project details? get a quote