# Share how you evaluate a new tool – 30 Days of Tools, Day 3

**URL:** https://club.ministryoftesting.com/t/share-how-you-evaluate-a-new-tool-30-days-of-tools-day-3/53356
**Category:** 30 Days of Testing
**Tags:** tools, 30-days-of-tools
**Created:** [2 October 2021 19:00 UTC](https://club.ministryoftesting.com/t/share-how-you-evaluate-a-new-tool-30-days-of-tools-day-3/53356 "2021-10-02T19:00:46Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![anne-laure](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/anne-laure/32/8630_2.png) [@anne-laure](https://club.ministryoftesting.com/u/anne-laure)
#### Post date: [3 October 2021 12:33 UTC](https://club.ministryoftesting.com/t/share-how-you-evaluate-a-new-tool-30-days-of-tools-day-3/53356/4 "2021-10-03T12:33:22Z")

</div>

> [@](#):
>
> How do you discover all the things you like/dislike about a new tool?  
> What do you rely on to make a reasonable evaluation of a new tool?

- I love to explore new tools, like exploratory testing 🙂 I ask for feedback from relevant communities, read documentation, search online…  
Can the tool help me? How much is it? Is it working well?

> [@](#):
>
> How do you know you’ve found “the one”?

- It is never “the one” there is still pros and cons ☹

> [@](#):
>
> What is the biggest turn-off when evaluating a new tool?

- Time is my biggest problem. But I do agree poor documentation/support=\>NO GO!

---

_[View the full topic](https://club.ministryoftesting.com/t/share-how-you-evaluate-a-new-tool-30-days-of-tools-day-3/53356)._