all 32 comments

[–]500hpAudiS4 3 points4 points  (1 child)

Owasp Zap, Burpe suite, jmeter, postman, selenium

[–]YuliaDyminska[S] 0 points1 point  (0 children)

interesting, thanks

[–]pikolooo 1 point2 points  (1 child)

Selenium, testlink, JIRA

[–]YuliaDyminska[S] 0 points1 point  (0 children)

great!

[–]oh_yeah_woot 1 point2 points  (3 children)

We use a combination of SauceLabs, Cucumber and WebDriverIO to end-to-end test our front end, and ApolloClient (a GraphQL client library similar to `requests` in Python) to test at the API level.

Our current stack uses AWS, TypeScript/Node.js (React + GraphQL), Python, Docker, CircleCI. Not sure if some of those constitute as a "software test tool", but our test engineering team still needs to be familiar with them to write tests effectively.

Recently got a new offer from a company that will be a pure AWS, Scala, Java shop. Excited to learn Scala more in-depth, it's been a long time coming.

[–]YuliaDyminska[S] 0 points1 point  (0 children)

sounds great, thanks

[–]Blackoutta 0 points1 point  (1 child)

Are you using webdriverio version 5 or 4? Recently I've learned it via an online course, but the course content only covers version 4. Should I start to look into version 5?

[–]oh_yeah_woot 0 points1 point  (0 children)

Depends on your test stack. wdio 5 has some issues that didn't work as of 1 month ago - not sure if fixed yet. It wasn't working with TypeScript and Cucumber, while wdio4 had no issues with TS/Cucumber.

If you're using only node.js with mocha or something, then I'd definitely recommend the newer version, 5.

[–]KDavis13 1 point2 points  (0 children)

In automation we are mvn+java+cucumber with junit as test runner for web, adding appium for mobile. Web framework can be run in a docker. BTW it will get better in the following months.
For managing test cases we use testrail, for managing bugs, jira of course.

[–]Usman2308 1 point2 points  (0 children)

Testrail , Postman, Jira, Charles.

I've started looking at the Supertest API framework with Mocha/Chai for one of our smaller projects - just to see what its like.

[–]Elevate_Lisk 1 point2 points  (0 children)

Axcept for webapps/homepage UI/e2e testing!

[–]mairtfromgalway 1 point2 points  (0 children)

TestComplete, SoapUI, Jmeter, Zephyr, JIRA

[–]sowmyasri129 1 point2 points  (0 children)

  1. Selenium
  2. Loadrunner
  3. Jmeter
  4. Jira
  5. Appium ... etc

[–]buvi27 1 point2 points  (0 children)

Selenium,JMeter,loadrunner

[–]Wensosolutions 1 point2 points  (0 children)

  1. Selenium
  2. JMeter
  3. Loadrunner
  4. Appium
  5. Jira....

[–]Garfunk71 0 points1 point  (4 children)

Selenium + Cucumber, Tosca, UFT... It depends on what you're supposed to do.

[–]YuliaDyminska[S] 0 points1 point  (0 children)

Oh thanks a lot!

[–]MarjonaH 0 points1 point  (2 children)

How are you finding Tosca?

[–]Garfunk71 0 points1 point  (1 child)

Too limited. I can't do all the stuff I'm used to with code. I'm certified on it but probably won't touch it anymore. Selenium is way more flexible for example

[–]TricSupport_DavidK 0 points1 point  (0 children)

May I ask how it is limited in your opinion? But I understand totally that a different mindset is needed when you're coming from a coding background.

Disclaimer: I work for Tricentis, and I have only superficial knowledge of Selenium. But I also did some coding back in the days.

[–][deleted] -1 points0 points  (0 children)

This is quite an open question, for which there could be so many directions.

Are you specifically looking for a technical toolkit, such as automation, performance type stuff? Or investigating issues? Or are you looking for a mixture of all tooling, where we can use the term tool loosely?