Test Cases

Test Cases

Creating Test Case Based on a Specific Test Type:

Test cases are usually documented by the QA team when the coding phase of the software development life cycle is in progress. While the development team works on building the software system, the QA team writes test cases that will help test the system once the code is ready. There are several types of test cases written based on the specific test type. Below are some of the common types of test cases written in the field of Software testing.

Functionality Test Cases:
Functionality Test Cases are written to check if the application’s interface work with it’s users and the rest of the system. These test cases are usually written by the QA team because the functionality test cases come under general QA processes. A typical example could be something like confirming a user if he has uploaded a profile photo.

User Interface Test Cases:
User Interface test cases are written to check if the Graphical User Interface (GUI) work and look as expected. Grammar and spelling checks, cosmetic inconsistencies, links and other factors that user see or interact with can be identified with these type of test cases. Cross browser compatibility issues are best tested with the user interface test cases. An example of user interface test case is to check if the website is best viewed on various screen sizes and devices.

Performance Test Cases:
Overall effectiveness and response times are validated with Performance test cases. How long does it take for the system to respond after executing an action is identified through performance test cases. These test cases are typically written by the testing team and are often automated. Performance test case helps understand the performance of application in real time scenarios. An example of performance test case is to check if the application is stable when multiple people login to the system.

Integration Test Cases:
The way two modules interact with each other is determined by Integration test cases. These test cases will help understand if the interfaces between multiple modules work fine or not. Either the development team or the QA team can write these test cases. Usually the QA team identifies the areas applicable for integration testing while the development team gives inputs on how these test cases should be written. An example of Integration test cases could be to check the link between home page and favorites section. When an item is added to favorites from home page, does it appear in the favorites section?

Usability Test Cases:
These test cases are often referred to as scenarios or tasks. They help identify how the application is used in a natural way by any user. Design team along with the testing team are usually responsible to write Usability test cases. What is the experience in adding items to a shopping cart is an example for Usability Test Cases.

Database Test Cases:
Database test cases are written to examine the application from database perspective. These test cases are usually written by those who have knowledge of SQL queries and Stored procedures. Did the application store the data at the right tables, did the stored procedure return the correct value are few of the examples of Database test cases.

Security Test Cases:
Security test cases are written to test the applications permission and actions wherever applicable. Penetration testing is driven using security test cases and factors such as authentication and encryption fall under this category. After ‘n’ number of login attempts, did the application lock is an example of a security test case.

User Acceptance Test Cases:
User acceptance test cases are usually broad and covers the whole of the application. By the time UAT starts, many other tests would have already been accomplished. The basic criteria of an UAT is not to find bugs but to check if the application is acceptable to end user.

Overall, it is necessary to have an idea of creating test cases based on the specific test type to ensure that the product or application is stable and free from bugs.

About SmartIMS – ConnX

Smart IMS – ConnX is a technology solutions oriented company integrating Application Development, Cloud Transformation Services, Managed Services and Professional Services.

As a leader in the unified communications field, Smart IMS – ConnX consistently delivers applications to enable users to be mobile, agile and competitive, helping enterprises to increase revenues, improve efficiency and mitigate risks. 

The company, headquartered in Plainsboro, New Jersey (US), with offices in India, Singapore, Sydney, deploys a global delivery model and deep domain expertise originating in the Trader Voice and Financial sector, with a focus on transforming traditional PBX to SIP-based telecommunications services. 
Smart IMS serves Fortune 1000 as well as emerging organizations across industries and geographies to transform their business from traditional model to cloud and digital. 

Our values and culture is focused to deliver quality, scalability, predictability in execution and an enhanced customer experience.

Get in Touch

Trust us to optimize your business through transformational enterprise solutions. Connect with us to learn more.

Scroll to Top