This document will lay out the deliverables and the responsibilities between Kontainers team and our customer’s Kontainers Edge/Enterprise Integration team. It also lays out the various test terms used in the integration program and what test deliverables are expected at each stage.
This section outlines the test strategy that will be adopted for testing for this project. The bulk of the product will be the existing, stable Kontainers SaaS product.
Where a new workflow or new UI functionality has been developed by agreement for the Customer, this new code falls under the test remit of this integration project
Timelines / Milestones
The Kontainers SaaS tenancy and engagement plan, agreed between the integration team over the course of the project, will identify the various test cycles.
Kontainers will provide an Account Manager as part of the implementation team. This person will be responsible for:
- Ensuring test plan is executed
- Ensuring that the Edge Customer is kept up to date on bug progress
- Work with customer on final bug list (if any) and prioritize for post project review
- Sign off of Kontainers product
We require a person and/or team from the Customer who can work with the Account Manager to deliver the final quality product.
Kontainers provides help files and is available to demonstrate the product to Customer test team.
This testing will test all the features of service or application on a test environment. For Kontainers delivered applications/features this testing would be done by the Kontainers team.
Kontainers uses an agile approach to development so functional testing is ‘per Story’. This means that as a new feature or capability is added the product it will be fully functionally tested before being handed to the customer Edge integration team
Installation and provisioning
These are tests to verify that the application/service can be installed and provisioned according to the install instructions. These are part of the standard Kontainers cloud management service.
Integration testing is the testing of interfaces between applications or different parts of applications. This could be for instance testing of protocols or testing of message flows. This testing will include negative as well as positive testing.
End to end Testing
End to end testing will be testing that the application/service being delivered works within an end-to-end environment. This means that testing of the application/service in an environment that includes all of the other systems that it interworks with – especially any customer designed UIs.
End to end testing will test if the functionality of the feature is accurate. This will overlap with acceptance testing where the Customer will verify if the integration produces the data results expected.
New applications need to be tested for redundancy (where applicable) and robustness. Testing would include verifying continued operation under error conditions such as the following.
- Network failure
- Connection failure
- Failure of other application
Similar to functional testing and may overlap somewhat. These are the tests that need to be run that are to verify that the functionality of the application is correct. Acceptance testing however would be run by the Customer and their team.
This testing should test the application and/or service from a customer point of view and should also test the application/service from a business process point of view. This would include such things as
- Verifying that the application as developed works with the intended business process
- Use real life examples to test the application/service
The sponsoring business function (Customer Care, Sales, Marketing) would be responsible for documenting and executing business tests.
It is at this point that the Customer will confirm all the ‘Business’ requirements have been met such as branding and security testing if mandated by your internal IT processes.
This is the final stage of testing prior to handover to production. This testing should be executed on the production environment immediately following installation of the application/service. Testing should focus on
- Ensuring that the product is installed and is operating correctly.
- Interfaces to all other applications are working correctly
- Data migration or conversion is done correctly
- All provisioning is done correctly
- Basic end to end functionality
Owner: For the initial deployment to friendly users this will be shared activity between Kontainers and the Customer and will be covered by Acceptance testing. However, when the product is live, any specific feature requests made at the Customer request can only be tested by the Customer for security reasons.
The types of testing below would not normally be within the remit of the integration project sign-off by the test teams. They are however important, so we describe the tests below and how they are supported outside the integration project.
Third Party System testing
This testing should test all the features of service or application on an external test environment. For Customer delivered applications/features this testing would be normally run by the Customer with Kontainers team help should it be needed (e.g. Test data, account provision etc.).
Unit testing is to be done by the developers and is not addressed in this test plan.
Production Monitoring tests
These tests would be run once the application/service is in production to verify that the functionality continues to work.
Scalability and Sizing
Scalability testing will be part of Kontainers operations processes and monitoring processes.
Performance testing on Kontainers SaaS is managed as part of the development process.
Copyright © Kontainers.com All Rights Reserved.