Test Case Design and Execution for Restaurant POS System Case Study

The Client

The client is a leading multi channel bill payment service provider in North America.

Their service is available from multiple access points as self-service kiosks, POS/clerk-assisted locations, smartphone applications and through other mediums.

The Challenge

Our client is the leading company which provides point-of-sale (POS) for the restaurant industry by combining cloud-based technology with mobile and social innovations. Its mission is to help every restaurant in the world succeed by turning transactions into insights.

Our client was looking for a testing partner that would fit into their agile- and scrum-based development life cycle. They needed a comprehensive QA strategy along with test case design and execution for new features, such as search hierarchy, day part report and multiple menu item, scheduled for winter release.

Tests needed to cover the following areas:

  • Core application features like editing, reports and management.
  • Web services testing.

The Process

  1. Learn system logic and functions.
  2. Design test cases and engage developers.
  3. Execute testing and report defects.

How Optimus Helped

To begin with, we learned the system’s business logic and functions by reading the client’s requirements and examining their application.

We then did test case design based on the requirement analysis using the following criteria for determining priority.

  • Critical test cases are the cases that test the main and basic features of the software.
  • High priority test cases are the set of test cases to ensure functionality is stable, intended behaviors and capabilities are working, and important errors and boundaries are tested.
  • Medium priority test cases test features and functions more detail. They include boundary test cases, negative test cases and configuration test cases.
  • Low priority test casestest some minor or small features and functions of the software.

We then let the developers review the test cases to get them involved in the testing as early as possible. Early communication with developers also helps prevent defects.

Finally, we executed the test cases, logged and verified the defects.

The whole project was successfully delivered on schedule.