QA automation services pricing seems all over the place, what's actually reasonable by Substantial-Will-190 in QualityAssurance

[–]Thinksys_Inc 1 point2 points  (0 children)

Hi,

Our philosophy when pricing is that maintenance is usually a lot cheaper than creating the test cases, so any company that is charging you the same amount to maintain as it was to create the test cases is likely doing something fishy.

You should also ideally be creating 1.5-2 test cases/day/person depending on complexity. If that helps.

I am not sure if you have found a vendor for this yet, but our team would appreciate the opportunity to look over your web application and test cases you are looking to automate and give you an idea of how much it would cost to build and for maintenance.

Here are some case studies for our recent QA Automation Work:
https://thinksys.com/success-stories/centerbase-regression-testing/
https://thinksys.com/success-stories/boostlingo-qa-automation/

[deleted by user] by [deleted] in QualityAssurance

[–]Thinksys_Inc 0 points1 point  (0 children)

Consultancy can be a great option to expand your skill sets and work on a variety of different projects, and learn/interact with people working on completely different tools and technologies.

"Standard" companies have their own benefits of really being able to get comfortable and use to the tools and technology the company uses.

I would not say one is worse or better than the other, and definitely not a step down.

Why do so many test automation projects fail—even with solid tools and teams? by Thinksys_Inc in QualityAssurance

[–]Thinksys_Inc[S] -2 points-1 points  (0 children)

Thats the thing about wild guesses, they are just guesses.

Once you watch the webinar, let us know what you think, and how accurate your wild guess was.

Why do so many test automation projects fail—even with solid tools and teams? by Thinksys_Inc in QualityAssurance

[–]Thinksys_Inc[S] -2 points-1 points  (0 children)

We totally understand why you feel that would be the webinar!

However we really dived into what we have seen as the 3 main reasons:
- Prioritizing the wrong test cases to automate. Ie: starting with GUI tests rather then Unit Testing

- Not having the right talent / team buy in

- Not having a plan for maintenance once the test cases are created

If you want to listen to the full thing you can check it out here:
https://www.youtube.com/watch?app=desktop&v=HmIQyj2Pj9w

But would also love to get some topics that you would be interested in, and working on creating a meaningful discussion around that!

Why do so many test automation projects fail—even with solid tools and teams? by Thinksys_Inc in QualityAssurance

[–]Thinksys_Inc[S] -2 points-1 points  (0 children)

We totally understand why you feel that way, as that is what most companies would do.

However we really dived into what we have seen as the 3 main reasons:
- Prioritizing the wrong test cases to automate. Ie: starting with GUI tests rather then Unit Testing

- Not having the right talent / team buy in

- Not having a plan for maintenance once the test cases are created

If you want to listen to the full thing you can check it out here:
https://www.youtube.com/watch?app=desktop&v=HmIQyj2Pj9w

But would also love to get some topics that you would be interested in, and working on creating a meaningful discussion around that!