Question Locked

QA Testing Data Setup

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi folks,

I work for a government agency in the US. I need to write some QA test scripts for an application that schools use to request buses for field trips. Buses are assigned in a particular order based on certain business rules. The QA testing environment needs to simulate the production environment as closely as possible.

I thought that maybe we could do this: 1) Copy data from production to staging (pre-production) and QA environments, 2) Submit bus requests in the staging environment and see what buses are assigned 3) Submit bus requests in the QA environment to see if the assigned buses are the same as the ones assigned in the staging environment.

Does anyone have any other suggestions for how to set up the testing environment?

Thanks in advance.

2 replies

by tony hopkinson

For instance it proves that any existing data works with the 'new' version.

Don't forget to take any database changes into account though. You should test your 'upgrade' script in staging as a prerequisite.

It depends on how your software is designed, but I'd want to do some tests that exercised the code for the buinsess logic.

E.g same bus can't be booked at the same time etc.

If you are real lucky and you have a spec, you should be able to develop tests from that the developer's should have met.

Also you should have a liason with the devlopers so they can suggest some non-apparent tests. Such as where a coding change to do one thing might impact another piece of functionality.

One thing I can't emphasise enough is do not be tempted to take short cuts.

Say do one transfer to staging back that up and then use that as a clean start. You can bottom problems like that, but any rework should be tested from scratch, at least before release, possibly more often if circumstances dictate.

HtHs

This discussion is closed to new replies.