Test Plan
From Meda360 Spec
(→Types of Testing) |
|||
| (2 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | + | <em>Note: The creation of the test plan was actually a essay question on the class final exam. The following content was selected from one student's exam because it represented the most accurate approach to a test plan for a project such as this.</em> | |
| + | <p> | ||
| + | == Types of Testing == | ||
| + | <p>Because the M.A.P project is designed primarily for potential media arts college students, user acceptance testing (UAT), along with functional testing, will be emphasized the strongest. | ||
| + | </p> | ||
| + | '''Functional Testing'''<br> | ||
| + | Before presenting the site for UAT, it will need to go through several iterations of functional testing. The site will need to be tested for compatibility with Windows and Mac, under the operating systems and browsers identified in the technical specification’s “target user technical environment.” | ||
| + | A team of three or four will scour through the website testing all links, loading of videos and images, correct navigation, consistency of information and formatting, and load times. This team will also be responsible for testing the site under the various operating parameters. The entire site will need to be combed through to make sure everything performs as expected (Freidlein, 206). This team will also do the minimal amount of operational testing necessary for any emailing functions. | ||
| + | |||
| + | '''User Acceptance Testing'''<br> | ||
| + | The development team will hold several focus groups where possible. The high schools, and ideally some of the students, which held focus groups during the project clarification stage will be used to get direct input. These students provided a key element in early project development and were willing to provide their opinions later in the project as well. The focus groups will operate in one of two manners, ideal with responses to both types. | ||
| + | <ol type="a"><li> | ||
| + | Students will be instructed to explore the website themselves, after a designated period of time general input and impressions will be gathered from the students. This will provide the development team with an uninfluenced opinion on the project. This could also be conducted as a survey sent to students. | ||
| + | </li><li> | ||
| + | Students will be guided by members of the development team through the website. This style of focus group will be more of a formal presentation to show prospective students what the website has to offer. After the short presentation, students will be asked for their opinions. | ||
| + | </li></ol> | ||
| + | Students will be specifically asked what they did and did not like, what they would change, which part of the project is most appealing, etc. In the event that the necessary number of groups can not be met with, information from the admissions office on students interested in both Pacific and media arts could be requested to contact students who could review the site. | ||
| + | |||
| + | '''Error Tracking'''<br> | ||
| + | Because multiple people will be finding errors as they test the website, a single spreadsheet managed by one person and posted to the project wiki is not efficient (Freidlein, 208). Instead, a page will be maintained on the wiki with a table tracking all the necessary information including who found the error, date, description, priority, who fixed the error, and the date it was fixed. | ||
| + | <p> | ||
| + | CITED: Freidlein, Ashley; <em>Web Project Management</em>; Morgan Kaufmann Publishing, 2001; 1-55860-678-5 | ||
<hr> | <hr> | ||
Next Section:[[Contact information]] | Next Section:[[Contact information]] | ||
Current revision as of 19:55, 19 December 2006
Note: The creation of the test plan was actually a essay question on the class final exam. The following content was selected from one student's exam because it represented the most accurate approach to a test plan for a project such as this.
Types of Testing
<p>Because the M.A.P project is designed primarily for potential media arts college students, user acceptance testing (UAT), along with functional testing, will be emphasized the strongest.
Functional Testing
Before presenting the site for UAT, it will need to go through several iterations of functional testing. The site will need to be tested for compatibility with Windows and Mac, under the operating systems and browsers identified in the technical specification’s “target user technical environment.”
A team of three or four will scour through the website testing all links, loading of videos and images, correct navigation, consistency of information and formatting, and load times. This team will also be responsible for testing the site under the various operating parameters. The entire site will need to be combed through to make sure everything performs as expected (Freidlein, 206). This team will also do the minimal amount of operational testing necessary for any emailing functions.
User Acceptance Testing
The development team will hold several focus groups where possible. The high schools, and ideally some of the students, which held focus groups during the project clarification stage will be used to get direct input. These students provided a key element in early project development and were willing to provide their opinions later in the project as well. The focus groups will operate in one of two manners, ideal with responses to both types.
- Students will be instructed to explore the website themselves, after a designated period of time general input and impressions will be gathered from the students. This will provide the development team with an uninfluenced opinion on the project. This could also be conducted as a survey sent to students.
-
Students will be guided by members of the development team through the website. This style of focus group will be more of a formal presentation to show prospective students what the website has to offer. After the short presentation, students will be asked for their opinions.
Students will be specifically asked what they did and did not like, what they would change, which part of the project is most appealing, etc. In the event that the necessary number of groups can not be met with, information from the admissions office on students interested in both Pacific and media arts could be requested to contact students who could review the site.
Error Tracking
Because multiple people will be finding errors as they test the website, a single spreadsheet managed by one person and posted to the project wiki is not efficient (Freidlein, 208). Instead, a page will be maintained on the wiki with a table tracking all the necessary information including who found the error, date, description, priority, who fixed the error, and the date it was fixed.
CITED: Freidlein, Ashley; Web Project Management; Morgan Kaufmann Publishing, 2001; 1-55860-678-5
Next Section:Contact information
