Hi, I came up with these thoughts after using the software.
Requirements to Consider
- Is there already a testing system in place?
- Is there a way to make use of it, if it exists?
- What is the current costs to maintain it?
- Does using another tool save us money in the long run?
- What kind of testing do we need to cover? Security, API, Regression, System, Acceptance?
- In what ways, could this project grow?
- Will there be more administrative features or employee features?
- Or will it target a different audience?
- What is the ease of use for the current and future testing software?
- Do we need to consider other testing software, if the current testing software applies to a different use?
- Example: Is accessibility testing needed? Is Cypress or other similar tool used?
Impact on Tool Selection
- How fast will that project grow? What kind of releases are we going to have?
- Will there be fast and small releases where the code changes often, or will there be long releases where the testers and developers have time to review the software before releasing it?
- What team skills do we have?
- How big is our team? Do many people do automation or programming or are they primarily manual testers?
- Do we have the capacity to maintain testing software?
- Do we have the capacity to write new tests?
- Who is going to get the most benefit out of the well-tested software?
- the managers?
- the employees?
- accountants?
- Is the tool going to help provide reporting to the expected audience?
- Does the future testing tool have an active support team and/or a community?