Scenario:
You work for an international company producing hardware and software for telecom networks. Hardware and software development is done in separate business units. You are the Test Manager of one of the network router software. In your product line, there is a long tradition of using an incremental lifecycle.
The hardware business unit produces a new version every six months. Software is developed in two-month increments. The business unit schedules are synchronized during design.
Your team consists of 15 testers, who have been in the company for two years or more. New tests are developed by the most experienced tester. Variations of tests and the regression test sets are run by the rest of the team.
The company management requires monthly progress reports listing the number of severe defects and the status of the test execution. Your company has also implemented CMMI on the company level. There have been problems to keep up with the hardware development schedule.
Your company originally has built an in-house automation tool as they anyway needed to build interfaces to drive test scripts against their system to fulfill all the telecom standard requirements.
Maintaining the in-house tool has gradually become very costly.
An open-source tool might provide you with some free time from your Test Automation execution. You need to consider several factors before making this decision. Which one of the following statements does not apply?
- Open-source tools are hard to be adapted.
- The licensing terms need to be understood.
- Telecom-standard compliance needs to be considered.
- Open-source tools have been created for a particular purpose.