Business Readiness Testing[BRT]

• As the name suggests Business Readiness Testing [BRT] is more concerned towards Customers readiness before the official launch of the project into Production.
• Business Readiness Testing [BRT] is conducted generally after UAT but before official go live , execution is performed by the business users (Note not the end users of the systems) , there are defined set of people who are invited for such testing activity and are trained to do a hands-on on real systems, so that they can teach further end users in their specific areas.
• This type of testing is helpful for the business users in identifying the real ground problems and the system capability to handle the real business scenarios.

Note : Business Readiness Testing [BRT] can also be done on Production Env.

Business Readiness Testing Activities

Below are the activities involved in BRT

• Identification of Business critical test scenarios.
• Environment readiness and business user id creation.
• Collecting all the required Test data.
• Execution Reports
• Identification of any critical defect slippage if any.
• Identification of any business requirement slippage if any which would have huge impact.

BRT key Members

• Business Stake Holders for each specific module.
• Important Business persons from each business circle.
• Business Analysts and Solution Architects.
• Testers
• Developers

Production Shake Out Testing

What does Production Shake Out testing Mean ?
Name of this testing clearly signifies that testing is done on Production Environment. This testing is a synonym for Sanity testing meaning running a soft check for some selected scenarios which would give a  confidence that new release was successful.
What should be tested ?
This kind of testing also includes checking that all the software systems are accessible in the environment.
Test Scenarios include scenarios from the current release and also some regression test cases are also required to be run.
Who Tests ?
Basically Testers are the persons who are doing such tests , but the testing is always supported by development team.
Why it is required?
This testing is required as this would help early detection of the problem, after the production deployment.
Time of testing ?
This kind of testing is carried out  immediately after the Production Deployment and in odd business hours, so that business is not affected by such testing.

Activities Involed Production Shake Out testing

Below are the activities involved in Production Shake Out test:

• Identification of Test Scenarios which needs to be run.
• Test user id creation in Production Env.
• Collecting all the required Test data.
• Execution Reports
• Identification of any critical business scenario issues if any ( both from existing and new functionality perspective).

Deliverables :

• Test Cases execution status.
• Defects/ Issues found if any. ( this may be technical or functional issues)
• Detailed Testing Report for all systems and high-level business scenarios run.