IM Server Load/Performance/Stress Compliance Test Specification - AlanKao

IM Server Load/Performance/Stress Compliance Test Specification

1. Introduction
   1. Purpose

This Compliance Test Specification for the GMIMPS supports the following objectives:

•       The GMIMPS includes the client and the server parts. For the server part, there are two main components: one is the control (Controller) and the other is Core Message (GMIMC). For the client part, it supports MTK (MRE), Android, iPhone, Symbian, Windows Mobile and etc and any kinds of the PC platform such as Win32, Win64, Linux and so on.

•       For easy testing, the server test environment will use Win32 with cygwin environment (please refer the cygwin official website: http://www.cygwin.com/ ) instead of the handset and simulation. If tester wants to test the client part, he should follow the Client test plan.

•       The GMIMPS Server architecture will be as the below:

 

1. 1. Background

The GMIMPS Server CTS will cover the Controller (GMIM Core Server), and GMIMC (GMHSDC and GMIMCloud). The GMIMCloud is the General Mobile IM cloud system which includes the DB cluster, DB failed over, DB load balanced and DB redundancy functions.

1. 1. Scope

There are five main parts of the GMIMPS Server: unit test, integration test, performance test, stress test and load test in the document and we spilt twelve test part on Chapter 4. The work flow chart of GMIMC is as the below:

 

1. 1. Project Identification

The table below identifies the documentation and availability used for developing the CTS:

1. Requirements for Test (Environment)

The listing below identifies what environment of items cases, functional requirements, and non-functional requirements as targets for testing. This list are necessary as below:

1. Windows XP / Windows 7 32 bits /Windows 7 64 bits
2. Cygwin / Python /JSON
3. Windows Command (CMD)
4. Visual Route 2010
5. Deliverables

6. [In this section, list the various documents, tools, and reports that will be created, by whom, delivered to who, and when delivered.]

    

7. Test Model

8. [This section identifies the reports that will be created and distributed from the test model. These artifacts in the test model need to be created or referenced in the ASQ tools.]

9. Test Logs

10. [Describe the method and tools used to record and report on the test results and testing status.] 

11. Defect Reports

12. [In this section, identify the method and tools used to record, track, and report on test incidents and their status.]

13.  

    Below are the test-related tasks:

         Plan Test

14. • identify requirements for test
    • assess risk
    • develop test strategy
    • identify test resources
    • create schedule
    • generate Test Plan

15.      Design Test

    -      prepare workload analysis

    -      identify and describe test cases

    -      identify and structure test procedures

              -      review and assess test coverage     

         Implement Test

16. • record or program test scripts
    • identify test-specific functionality in the Design and Implementation Model
    • establish external data sets

17.      Execute Test

              -      execute Test procedures

              -      evaluate execution of Test

              -      recover from halted Test

              -      verify the results

              -      investigate unexpected results

              -      log defects

         Evaluate Test

              -      evaluate Test-case coverage

              -      evaluate code coverage

              -      analyze defects

              -      determine if Test Completion Criteria and Success Criteria have been achieved