Agile Acceptance Testing – is a mix of traditional functional testing and traditional acceptance testing because the development team and their stakeholders are doing it collaboratively. Developer testing is a mix of traditional unit testing and traditional class/component/service integration testing.
ii. Developer Testing – strives to verify the application code and the database schema and to look for coding errors, perform at least coverage if not full path testing, and to ensure that the system meets the current intent of its stakeholders. It is often done in a test-first manner, where a single test is written and then sufficient production code is written to fulfill that test. (Ambler, Agile Testing Strategies)
b. Investigative Testing – This strives to discover problems that the development team didn’t consider. Agile teams produce working software at the end of each construction iteration and hence a new version of the system should ideally be given to a separate test team that which can be assigned the goal to explore potential scenarios that neither the development team nor business stakeholders may have considered. (Ambler, Agile Testing Strategies)
2) Release – At this stage, the project
is ready to be delivered to the user and is tested from user acceptance point of view at this stage.
3) Production – Once the system has been delivered, defects may arise and Agile testing ensures that these defects are fixed in a timely and appropriate manner.
These are just random excerpts of essays, for a more detailed version of essays, term papers, research paper, thesis, dissertation, case study and book reviews you need to place custom order by clicking on ORDER NOW.