Your organization has just hired a test automation architect who has previously worked on medical software with strict regulatory requirements. His test automation framework is very solid and will allow the staff to build maintainable data-driven test cases. His tool choice is the top of the line tool that has been used for many years for traditional test automation. You are concerned that this is a very expensive tool and may not have the flexibility needed in your environment, particularly since the mobile applications your company develops are intended to exist in the market for only six months before being re-worked to add new features and change the user interface. The software development life cycle is iterative and the team uses continuous integration to provide testable software faster.
Given this information, what should you recommended for the test approach?
A is correct. It is important to use tools that are well suited for mobile. Keyword-driven test automation is likely to be more maintainable than data-driven, particularly when the application changes frequently. B is incorrect because high re-usability is not a goal for this project. High levels of coverage are probably not important in the test automation because the product has a short lifespan. Also, the tools may not be well-suited to mobile products. C is not correct because bypassing test automation violates the rules of the iterative lifecycles and would miss the opportunity of automating testing after the continuous integration occurs. D is not correct because the test automation should be used for the functional testing and needs to be done early in the lifecycle to ensure good product development and continuous integration testing.
Currently there are no comments in this discussion, be the first to comment!