Skip to content

Commit

Permalink
fixtype2
Browse files Browse the repository at this point in the history
  • Loading branch information
faraycloudx committed Oct 30, 2023
1 parent 6ce7202 commit b5072e4
Showing 1 changed file with 8 additions and 16 deletions.
24 changes: 8 additions & 16 deletions posts/faraycloudx/Invest-on-testing-tool.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,15 +7,11 @@ cover_image: ./assets/testing-tool/coverTestingTool.webp

## Overview

A common topic on software development process is the budget for testing tools. Nowadays is still common see multiple
excel sheets for test cases, emails with bug reports or documents with regressions suites reports. Because of this he market offers a large number of testing tools, but not every tool can be right for you
and is sometimes part of our job explain why the client or the team should invest part o the budget on a testing plugin
or a testing management tool. In the article below I will try to explain some of the main reasons of include this powerfull complements on your project.
A common topic in the software development process is the budget for testing tools. Nowadays it is still common to see multiple excel sheets for test cases, emails with bug reports or documents with regressions suites reports. Because of this the market offers a large number of testing tools, but not every tool can be right for you and is sometimes part of our job to explain why the client or the team should invest part of the budget on a testing plugin or a testing management tool. In the article below I will try to explain some of the main reasons to include these powerful complements on your project.

## How much do a testing plugin or complements cost?
## How much does a testing plugin or complements cost?

There are multiple management tools on the market like Jira, Azure Devops that are used around the world but the testing plugins are not all free and sometimes the free options do not meet the needs of the team.
Let's see some prices of the most common plugins available on the market:
There are multiple management tools on the market like Jira, Azure Devops that are used around the world but the testing plugins are not all free and sometimes the free options do not meet the needs of the team. Let's see some prices of the most common plugins available on the market:

### For Jira

Expand All @@ -26,19 +22,15 @@ Let's see some prices of the most common plugins available on the market:
**Testrail Professional Cloud**: USD $408 per user, per year.
**Testrail Professional Server**: USD $8140 Up to 10 users, per year.

## What should you consider to make a choose?
## What should you consider to make a choice?

First you need to know what types of testing are you going to do and make sure the plugin or complements you want to buy have the set that enables you to perform all the tasks. Consider that this tool is going to make your work easier but also needs to be useful for your partners on your team. For example: reports, real-time test results, management of test cases, test executions, regressions suites, option to create and store scripts, integration with automated testing frameworks, continuous integration are some of the main features you need to consider.
Second, consider also the documentation or support that the tool has, because it's important also have a good support just in case you will have issues on installation or use.
Third, make sure that the tool should help you and your team with the development work. The tool should adapt to your processes not the opposite.
FFirst you need to know what types of testing are you going to do and make sure the plugin or complements you want to buy have the set that enables you to perform all the tasks. Consider that this tool is going to make your work easier but also needs to be useful for your partners on your team. For example: reports, real-time test results, management of test cases, test executions, regressions suites, option to create and store scripts, integration with automated testing frameworks, continuous integration are some of the main features you need to consider. Second, consider also the documentation or support that the tool has, because it's important to also have good support just in case you will have issues on installation or use. Third, make sure that the tool should help you and your team with the development work. The tool should adapt to your processes, not the opposite.

## How to sell the plugin idea to your team?

Prepare a brief presentation: include all the features that the tool has to offers and prepare it considering if its going to be presented to a client or to your team. Would be good if you include some examples of others projects that are already working with it.
Estimate the number of users that are going to use it: Remember that the cost usually is attached to this, so consider just the main users to reduce the cost.
Includes the price per year: this allows you to have access to it sometimes even on earlier stages on the projects and you can get familiar with it.
Search if exist a live demo of the tool: some of the tools have a live demo or a free trial that you can use it to explain the benefits of buy it.
Prepare a brief presentation: include all the features that the tool has to offer and prepare it considering if it's going to be presented to a client or to your team. Would be good if you include some examples of others projects that are already working with it. Estimate the number of users that are going to use it: Remember that the cost usually is attached to this, so consider just the main users to reduce the cost. Includes the price per year: this allows you to have access to it sometimes even on earlier stages of the projects and you can get familiar with it.
Search if there exists a live demo of the tool: some of the tools have a live demo or a free trial that you can use to explain the benefits of buying it.

## Conclusion

Remember that all tools are good but not all are good for all teams or projects. Before choose make a research and evaluate always the needs. Not always the more expensive is the most usefull.
Remember that all tools are good but not all are good for all teams or projects. Before choosing, do research and evaluate the needs. Not always the more expensive is the most useful.

0 comments on commit b5072e4

Please sign in to comment.