LAB 3 ELDERS Prototype Test Plan/Procedure

1

LAB 3 – ELDERS Prototype Test Plan/Procedure

Lab 3 – ELDERS Prototype Test Plan/Procedure

Team Purple

Josh Fetherolf, Team Purple

CS411w

Janet Brunelle

April 17, 2013

Version 1

Table of Contents

1 Objective

2 References

3 Test Plan

3.1 Testing Approach

3.2 Identification of Tests

3.3 Test Schedule

3.4 Fault Reporting and Data Recording

3.5 Resource Requirements

3.6 Test Environment

3.7 Test Responsibilities

4 TEST RESPONSIBILITIES

5 TEST PROCEDURE

5.1 Test Case Names and Identifiers

6 TRACEABILITY TO REQUIREMENTS

List of Figures

Figure 1. Major functional component diagram.

List of Tables

Table 1. ELDERS prototype test cases by category.

Table 2. ELDERS prototype test schedule.

Table 3. ELDERS test case chart.

Table 4. ELDERS traceability matrix.

(This space intentionally left blank.)

1 Objective

Endangered Languages Documentation Extension and Revival System (ELDERS) is a product being developed by the Old Dominion University (ODU) CS411 Purple Group. The purpose is to assist in restoring and expanding endangered languages. When a language becomes extinct, it can have a devastating effect on the culture. Revival systems are commonly made up of a database that includes all the words and definitions that are known and documented, including pronunciations, syllables, sentence structure, and other grammatical tips associated with the words. ELDERS is a web application that users can access to learn about the speaker’s history, language, games, and access a dictionary of words belonging to the language.

The prototype has been designed using the Nottoway Tribe of Virginia, local to the Tidewater area. They have a language that is currently classified as endangered. Any society can use the ELDERS web application to restore their language just as the Nottoway is restoring theirs. There are many tribal members cooperating and assisting with the project to help build the database of words.

The main objectives of the prototype are to prove that that the system is versatile and able to be used anywhere the user requires it. It is educational in its execution so that the user is learning the language correctly. The system is efficient in attaining the maximum desired effect without overwhelming the user with information. Additionally, the system is to be well documented in its sources to provide a useful database. The community of the language will be involved to assist with documentation. In the end, the group would like the system to be free and available to anyone who wants to utilize it.

2 References

Fetherolf, Josh. (2013). Lab 1 – ELDERS Product Description. Yorktown, VA: Author.

Fetherolf, Josh. (2013). Lab 2 – ELDERS Product Description. Yorktown, VA: Author.

The Week Staff (2012, June 22). Google’s next mission: Save dying languages – The

Week. The Week Magazine: Political News and Cartoons, Current Events and Entertainment Online. Retrieved October 8, 2012, from

3 Test Plan

The test plan discusses the tests that will be performed, the schedule of testing, how the tests will be reported, resource requirements, testing requirements, and responsibilities of each team member.

3.1 Testing Approach

The implementation of the ELDERS prototype will be checked by a combination of component and application tests. There are twelve testing categories that, by testing individually, will serve as the test for the web application itself.

Figure 1. Major functional component diagram.

The first testing category will show how access to the application is controlled. The access control tests show that the system can have users create accounts, request tier status, and that the information is modifiable. The second category demonstrates basic login actions. Tests in this category are designed to confirm that usernames and passwords are valid or make changes to their account settings. The third testing category tests the voting algorithms. Council members will have the ability to vote on suggested words, and when enough votes have been obtained, the word will be entered into the database and become documented as belonging to the language. The fourth testing category will determine how the search function works. Aspects of the search function such as returning information or displaying proper sections will be confirmed. The fifth and sixth testing categories related to the non-word educational aspects of the application and establish that the Nottoway’s history and games sections are present. The seventh testing category verifies that users can make suggestions to the database. This component is critical to the application actually expanding the language. The eighth testing category tests the application’s administration of the website. The ninth testing category confirms that the forum is accessible and functioning. The forum allows group members to discuss possible word suggestions, as well as aids in reviving the language by providing an environment for using the endangered language. The tenth testing category relates to the database of ELDERS. The database houses the historical dictionary and the expanded dictionary. The eleventh testing category validates user access to the dictionary and grammatical aspects of the language. The final testing category tests the versatility of the application by confirming viewing on various devices.

All tests are scheduled in a controlled classroom environment using the ODU network and hardware. Test users will be conducting the tests with results being confirmedby observation. Back-end logs will be being monitored to make sure all information is transferred through the system.

3.2 Identification of Tests

Table 1 identifies the twelve test case categories that will be performed with the description of specific components.

Table 1. ELDERS prototype test cases by category.

3.3 Test Schedule

The ELDERS group has been given 45 minutes to setup and explain the prototype. The first five minutes will be used to setup our test area; following will be going through the test cases shown in Table 2.

Table 2. ELDERS prototype test schedule.

3.4 Fault Reporting and Data Recording

There will be a test recorder to observe each test and record the results with a pass or fail as well record any necessary comments. The test recorder will have the pre-printed test cases and will mark the tests with a pass or fail. If a test fails, the test recorder will document the conditions surrounding the test and any error messages. The database will be monitored to assure that a test has actually passed. This is to make sure the front-end of ELDERS is cooperating with the back-end.

3.5 Resource Requirements

The ELDERS prototype demonstration will require that the virtual machine be working and running on the ODU server. The test user will be seated at the desktop that is displaying ELDERS on to the projection screen. The test user will access the ELDERS webapp and test the test cases. The database monitor will be on a laptop that can access the database that lies on the ODU servers virtually.

3.6 Test Environment

The prototype demonstration will be held in the conference room in Dragas Hall. The designated test user(s) will be on the computer that is at the end of the rectangle table. The database monitor will be located next to the test user(s) with the laptop. The test user(s) and database monitor will test network connectivity before the starting of the prototype presentation. The presenters will be at the front of the room near the projector screen. The test recorder will be sitting away from the presenter, but close to the test user(s) to make sure all test cases are recorded and documented.

3.7 Test Responsibilities

In the ELDERS prototype presentation, there will be two presenters, two test users, a database monitor, and a test recorder. The primary speakers will be Tatiana Livingston and George Calhoun, who will work together in presenting the prototype. They both act as backup for any presenter who may be unable to attend. They will also provide an introduction and narrative of each test case. Ben Cortina and Josh Fetherolf will be test users as well as operating the computer. Taking turns, each test user will execute the test case, explain what they are doing as well as show the expected results. Terry Stilwell will be the database monitor, responsible for displaying and explaining changes to the database when applicable. Robert Matson is the test recorder. He will keep the testing on track and will record what has been done and the result. He will also record what needs to be done should any errors occur.

Table 3. ELDERS test case chart.

4 TEST RESPONSIBILITIES

In the ELDERS prototype presentation, there will be two presenters, two test users, a database monitor, and a test recorder. The primary speakers will be Tatiana Livingston and George Calhoun, who will work together in presenting the prototype. One of the two presenters will take the other’s job if he/she is unable to attend. They will also provide an introduction and narrative of each test case. Ben Cortina and Josh Fetherolf will be test users as well as operating the computer. Taking turns, each test user will execute the test case, explain what they are doing as well as show the expected results. Terry Stilwell will be the database monitor, responsible for displaying and explaining changes to the database when applicable. Robert Matson is the test recorder. He will keep the testing on track and will record what has been done and the result. He will also record what needs to be done should any errors occur.

5 TEST PROCEDURE

A detailed set of test cases has been prepared for testing ELDERS. Each test has been designed to ensure that the ELDERS prototype meets its requirements. These tests will be described in Section 5.1.