1 Integration and Systems Tests

Please refer to the notes provided in CS 350 on Systems Testing.

Last week we scripted the set of unit tests to be executed. As explained in CS 350, automation of tests simplifies regression testing after anything in the code has been modified. The aim is to affirm that all versions of the code perform as expected.

Now, we have to put the units/components together as a working system. In some cases the component may be an existing piece of software or a legacy system. We must write specially developed code to perform I/O activities in the process of adding functionality to an already working system.

Another example is combining a back-end database with a front-end User Interface. In this example, integration tests would be needed to confirm exchange of data. Is the UI able to pull information from the database, and similarly, push information to be stored?

In this same example, a systems test would be used to verify that the correct data was pulled and pushed in the appropriate situation (execution of code) while using the system. A system test case will verify already executed unit tests. Every time the user clicks “submit” they are retesting the unit test that verifies the webpage was designed appropriately (there exists a submit button), that the database table to be populated was developed (there is a place for the data to be stored) and that the action executes correctly (the data is stored).

Acceptance tests will not be addressed other than to state their purpose. The customer typically creates the requirements and/or cases. They expect a particular attention to detail. For example, they may know that the data is transfer must be completed in less than .3 seconds to prevent failure in their environment.

2 Examples of Integration and System Test Cases

2.1 TPOT Instructor Dashboard

3.1.1.1 Login

This section details the login process for users of the TPOT Instructor Dashboard. Users will be directed to login through a Google account, which will return email address information to TPOT’s web server and direct the user to the Instructor Dashboard tabbed home page. TPOT Instructor Dashboard login must conform to the following functional requirements:

3.1.1.1.1 Unauthorized users who visit the dashboard page must be presented with an option to log in using a Google account.

3.1.1.1.2 Authorized users must be limited to the following user types:

    a. Instructors
    b. Teacher’s Assistants

3.1.1.1.3 Users authenticated by Google must have their validated Google email checked against the TPOT database to determine that the email address is present in the database User Table (see 3.1.3.2.4).

3.1.1.1.4 Users authenticated by Google must have their validated Google email checked against the TPOT database to determine that the email address is that of an Instructor or Teacher’s Assistant (see 3.1.3.2.4).

3.1.1.1.5 Authenticated Instructor and Teacher’s Assistant users must be redirected to the instructor dashboard tabs page.

2.2 TPOT - Activity Tab

3.1.1.2.1 Activity Tab (Josh)

This section details the Activity Tab, which allows Instructors and Teacher’s Assistants to view the Activities performed by users of all modules of TPOT. For complete details of what constitutes an Activity, see section 3.1.3.3. The Activities Tab must conform to the following functional requirements:

3.1.1.2.1.1 Must allow authorized users to view the following attributes of Activities:

    a. Course
    b. Team
    c. User email address
    d. Activity Type
    e. Date Accomplished (YYYY-MM-DD HH:MM:SS)

3.1.1.2.1.2 Must allow authorized users to sort Activities by the following attributes:

    a. Course
    b. Team
    c. User email address
    d. Activity Type
    e. Date Accomplished (YYYY-MM-DD HH:MM:SS)

3.1.1.2.1.3 Must allow authorized users to filter Activities by the following attributes:

    a. Course
    b. Team
    c. User email address
    d. Activity Type
    e. Date Accomplished (YYYY-MM-DD HH:MM:SS)

3 More Recent Examples

Let us take a look at a few more recent groups:

3.1 Polymorper - TextBook UI Test

Level Dependent UI shall display the “Textbook” curriculum by breaking down the learning sections before and after each puzzle/challenge.