BSA 375 Week 4 DQ 1 - a phase thats added later. Starting...

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
Speaking in terms of traditional development models, testing can be seen as a distinct phase which only  begins after the development phase is completed. In a lot of software engineering methodologies, testing  is carried out as a separate phase post implementation. The merit in doing so is that it would be much  faster for a fresh eye to identify obvious defects than to expect developers to find their own mistakes. All  methodologies however do not view testing as separate phase that only occurs at the end. For example,  in Agile methodology, Quality Assurance (QA) teams treat testing as a continuous process that is applied  to measure quality and give feedback. Agile views testing as a process that evolves gradually and not as 
Background image of page 1
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: a phase thats added later. Starting application testing with development creates continuous test cycles which allow developers to single out application issues as and when they get introduced and act on them immediately, instead of waiting till the end for the testing phase to being and detect the error after several cycles. Testing tools help automate test cases; evaluate performance, functionality, scalability, and load; improve speed (when compared to manual testing); cut down on manual effort; reduce human resource requirement; and decrease human error. Selenium and QTP are examples of regression testing tools, whereas, LoadRunner and NeoLoad are examples of load testing tools....
View Full Document

This note was uploaded on 11/21/2011 for the course BSA/375 BRBSIT911 taught by Professor Shawnpullum during the Spring '10 term at University of Phoenix.

Ask a homework question - tutors are online