System Testing Part 2 ~ Tumblia Test Solution

Here is the demonstration how you can do System Testing

Development Server:

It is the combination of hardware(HDD) and software which is use to store the code written by the developer.

Testing Server / Test Bed:

It is the combination of hardware(HDD) and software which is mainly use to install the software that needs to be tested.

Production Server:

It is a server present in the customers place where customer can use the software and run the business.

Testing server similar to production server diagram

Explanation:

1st Test Cycle:

1. Customer gives the requirement for A-Z modules in the form of customer requirement specification (CRS) business analyst will convert customer requirement specification (CRS) to software requirement specification (SRS) and architect will do design (High level Design and Low level Design).

2. As part of module 'A' customer has given requirement as first name text field(Fn),last name text field(LN),user name text field(UN),password text field(PWD),employe ID text field(EID) and gender radio button(Gen).

3. Development lead will assign features to developers like 1st developer will develop first name text field(FN) and last name text field(LN), 2nd developer will develop user name text field(UN) and password text field(PWD),3rd developer will develop employe ID text field(EID) and 4th developer will develop gender radio button(Gen) as you can see in the above picture.

4. All the developers will write the code for module 'A' and they will do white box testing compress the code and store in development server in zip format in the below mentioned path D://Build/ B01.zip.

5. Development lead will send a mail to test lead stating that build B01.zip is ready for testing, it consist of code for module 'A' and white box testing is completed.

6. Test Lead will connect to development server(Dev) copy paste build B01.zip into testing server then unzip and install the build and test lead will give url, user name(UN) and password(PWD) to test engineers and assign the features to test engineers like 1st test engineer will test first name text field(FN) and last name text field(LN), 2nd test engineer will test user name text field(UN) and password text field(PWD),3rd test engineer will test employe ID text field(EID) and 4th test engineer will test gender radio button(Gen) as you can see in the above picture.

7. Every test engineer will do functional testing(FT) for module 'A' while doing functional testing if test engineer find any defect test engineer will login to defect tracking tool (DDT) prepare defect report by giving unique defect ID and communicate defect to development lead and development lead will assign defect to respective developer.

8. Parallely developers will be Writing code for new module 'B' and Fix defects in module 'A'

then he will do white box testing for module 'B'

9. Development lead or developer will compress the code store the code in development server in zip format in the below mentioned path D://Build/ Bo2.zip.

10. Development Lead will send a mail to test lead stating that build B02.zip is ready for testing, it consist of code for module 'B',20 defect fixed for module 'A' and white box testing is completed.

2nd Test Cycle

1. Test Lead will connect to Dev server copy paste build B02.zip in testing server unzip uninstall old build install new build.

2. Test Lead will assign features to test engineer and ask them to start the testing.

Test Engineer should first do functional testing (FT) for module 'B'.
Then Integration Testing (IT) between module 'B' and 'A'.
Then Retest the defect in module 'A' (Test Engineer retest defect which is found by him not worry about defect found by other test engineers).
Test old modules

Like this way testing continuous for many cycles (till 25th) once test engineer get to know that minimum bunch of modules are ready then testing team will talk to production team and get testing server similar to production server setup available.

In this server testing will mainly focus on doing system testing. Assume that testing continuous from 26th to 55th cycle.

For example till module 'P' is completely tested now for 'Q' module development lead will compress the code store the code in development server in zip format in the below mentioned path D://Build/ B026.zip.

Development Lead will send a mail to test lead stating that build B026.zip is ready for testing, it consist of code for module 'Q',45 defect fixed for module 'A-P' and white box testing is completed.

26th Test Cycle

1. Test Lead will connect to Dev server copy paste build B020.zip in testing server similar to production server unzip uninstall old build install new build.

2. Test Lead will assign features to test engineer and ask them to start the testing.

Test Engineer will first do functional testing (FT) for module 'Q'.
Then Integration Testing (IT) between modules 'A-Q'.
Then do System testing (ST) for all the modules.
Then Retest the defect in modules 'A-P'.
At last test the old modules

Assume that developer will give module 'Z' in 50th cycle now test engineer will test module 'Z' once after testing is completed last 4-5 cycles requirement will be freezed developer will be fixing old defect and test engineers will be testing old defects and in the end moment also again test engineers will do functional testing (FT), integration testing (IT) and system testing (ST) for all 'A-Z' modules.

Once the software quality is good testing team will communicate to project manager, development manager and testing manager stating that software quality is good and finally software will be deployed or installed in the production server so customer can use the software and run the business.

This is how system testing works in the real time.

Why test engineer finds new defects while testing old modules ?

Chances are there developers adding new module might introduce defects in old module.
Chances are there developers fixing defect in old module might introduce defects in same module.
Chances are there test engineer might have missed defects in previous cycle.

When to go for system testing ?

When minimum bunch of modules are ready.
When testing server similar to production server setup is available.
When the product is relatively stable (No Blocker defect).
Basic functionality of all the module should be working fine.
When we start getting less number of requirements.

What do you mean by testing server similar to the production server ?

1. Hardware should be similar to the production server:

Manufacturer should be similar:- It means if production server is manufactured by HP then testing server similar to production server should be manufactured by HP only.
Configuration and make should be similar but we can have different capacities (It means number of cpu and storage can be different).

2. Software should be similar to the production server:

Operating System should be similar to the production server.
Web server should be similar to production server.
App server should be similar to production server.
Database server should be similar to production server.

3. Data should be similar to the production server:

It means if production server is having 50000 user account then testing server similar to production server should have dummy data (Dummy Accounts).
Creating 50000 account manually is very tough job so in the company we go for automation.