Updating the test case document: GeneralSetup

Describes whether applications, tools, or software packages, such as an email server, Payment Gateway simulator, or back-end stubs, must be configured for the test cases to run.

• Provide a list of what must be configured before the test cases can be run.
• Document the server-side configuration. Depending on the division of responsibilities, it is acceptable for the Application Setup instructions to outline what must be configured on the server, but not how this can be done.
• Indicate which ones must be set up one time and which ones must be set up each time a new store is deployed or updated.

Describes the stores that must be set up for running test cases in multi-store projects. Provide a brief description of each store that the tester must be aware of. Include stores that are not meant for shopping, such as asset stores, depending on whether the FVT team must be made aware of them or has test cases run against them.

• Provide a list of the stores on the system and a brief description of what each store represents.
• Update the steps to publish the store.
• Update any store page changes that must be done before you run the test cases.

Describes what data must be loaded in the database or available to the client environment before you can run the test cases.

• The SAR file with your data must be created and published to the test environment or your data must be loaded using loading facilities.
• Include any specific test data that is needed for multiple test cases. You can include users, organizations, promotions, or any other customized data required.

Describes the environments that are needed for testing.

• Describe where to get and how to set up the tools and software that is needed for testing in the client side.
• Detail client side configurations in full as all testers must follow these instructions. Browser settings, tools, and other configurations that affect the testing must be detailed.