We at SWQA India perform ERP testing for our clients wherein level requirements for testing of ERP is done using a test plan that covers following areas:
Our ERP testing covers both functional and non-functional areas.
- Identify existing project information and business scenarios which shall be tested
- List recommended business functions for testing
- Recommend and describe testing approach that will be used while testing the application
- Identify required resources
- List the deliverable elements of the project
The goal of this testing activity was to make the “Go-Live” decision. Sometimes due to time constraints it is not possible to conduct normal exhaustive testing activity. Our specialized team of people ensures proper decision making in the constrained time period decided to “Go-Live” decision on the basis of “Business Scenarios” supported by the SUT -System Under Test. The purpose of the test plan is to define a framework for identifying, prioritizing, design, executing and verifying results of tests based on “Business Scenarios”.
The SUT - System Under Test is an ERP product which has to handle the transactions of a company operating out of multiple locations, dealing in multiple products conducting business multiple entities. Hence it is critical for the testing process to address the business needs at a larger level. Keep this view point in mind we follow a testing process that is driven by “Business Scenario” approach.
The SUT - System Under Test is an ERP product which has to handle the transactions of a company operating out of multiple locations, dealing in multiple products conducting business multiple entities. Hence it is critical for the testing process to address the business needs at a larger level. Keep this view point in mind we follow a testing process that is driven by “Business Scenario” approach.
Our ERP testing covers both functional and non-functional areas.
Functional Testing
Non Functional Testing
Test Objective:
Ensure that the SUT - System Under Test supports the completion of the identified business scenario with proper flow of data from one business function to other.
Technique:
Valid business scenarios will be developed and validated from process owners. For these business scenarios test cases will be developed. Execute each function, using valid and invalid data, to verify the following:
All planned scenarios are successfully executed. All planned tests have been executed. All identified defects have been assigned to developer for fixing.
Ensure that the SUT - System Under Test supports the completion of the identified business scenario with proper flow of data from one business function to other.
Technique:
Valid business scenarios will be developed and validated from process owners. For these business scenarios test cases will be developed. Execute each function, using valid and invalid data, to verify the following:
- Creating, updating and deleting entries in each module
- Running complete scenario end to end
- Testing the transactions take place correctly
- Reports are properly generated
- Validation of User Roles
- The appropriate error / warning messages are displayed when invalid data is used
All planned scenarios are successfully executed. All planned tests have been executed. All identified defects have been assigned to developer for fixing.
In non functional Testing a separate environment is installed for the testing purpose. However this environment will be loaded on the same server as the development environment.
Hence a separate database instance along with a separate Application instance will be loaded for the QC purpose. This will ensure that the two environments will reside on the same server but will be separate without any effect on each other.
The production database backup will be restored from the tape on this server at frequent periodic interval. This will ensure that the test environment is exact replica of the production environment to produce accurate test results and also will serve as a cross test of the tape back up.
The Bugs encountered are reported in a Bug tracking tool called Bugzilla. The type of testing includes:
Hence a separate database instance along with a separate Application instance will be loaded for the QC purpose. This will ensure that the two environments will reside on the same server but will be separate without any effect on each other.
The production database backup will be restored from the tape on this server at frequent periodic interval. This will ensure that the test environment is exact replica of the production environment to produce accurate test results and also will serve as a cross test of the tape back up.
The Bugs encountered are reported in a Bug tracking tool called Bugzilla. The type of testing includes:
- Security Testing
- Maintainability Testing
- Reliability and Availability testing
- Load Testing
