In the future, what is the expectation for device capabilities?
When building a flexible testing framework, how does the short product life cycle affect the test approach and tool decisions?
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?
As life cycle models adapt to meet the needs of the mobile application market, how will the interaction between the developers and testers change?
What type of testing methodologies should mobile applications testers seek?
What types of testing are particularly important for mobile applications based on the user's expectations?
