Publishers of technology books, eBooks, and videos for creative people

Home > Articles > Web Design & Development > Usability

  • Print
  • + Share This
Like this article? We recommend

Testing Code

Several types of testing occurred simultaneously. Sting or unit testing occurred at the development level before passing the project to QA. System, integration, and acceptance testing occurred when the project came into QA. Regression testing happened when defect tickets were sent back to QA for retest.

To determine how much time to spend on testing, the rule was that QA should get about a third of the time it took to develop the site. QA's Sherry Valenti says, "The team usually got less than that. Overall, QA got about two weeks to test Informit and Exam Cram and three weeks to test all other network portals." She also notes that some of the resource time overlapped, as there was a one-week period when all portals would be in QA to be tested at the same time.

Test cases were determined by the requirements and prototypes for the rewrite. QA created the test cases using a matrix form and attempted to test all pages, functionality, interfaces, and database components.

QA reported errors through an open ticket to development and human factors, using a defect-tracking application. When the issue was resolved, the ticket was reassigned to QA for retest. If the ticket was retested successfully, the ticket was closed. If not, the ticket was reopened and submitted again.

  • + Share This
  • 🔖 Save To Your Account