DEV Community

Cover image for What to use in test cases? Two important tools in software testing

What to use in test cases? Two important tools in software testing

arobssoftware profile image AROBS ・3 min read

We believe in the importance of the perfect combination of software developers and software testers. At AROBS, we are happy to present our partners, not only great software development teams backed up by a strong cohort of software testers.
We picked their brains to find out what tools they use to make sure that every product they work on our IT outsourcing projects is bug-free.

So, they gave us a plethora of cool names, like Zephyr, Bugzilla, Selenium and many others. Curious? Read below all about them!

Let us start with the beginning. As about project documentation, they use Confluence. It allows you to keep all the information and documentation of the project in one place. You can have your personal space to keep the personal information and a space for your team that holds the information that can be shared. Also, one of their favourites is JIRA, a particularly useful tool for project management and bug tracking. It is easy to use and allows you to create, categorize, assign and solve an issue.

How do our testers manage test cases?

They say: try Zephyr. This is a test management software that allows performing application tests and keeping track of the results. The test management software is accessible to hundreds of people which makes it very useful to large companies or large testing teams. Being available to so many people, Zephyr also allows communication on a global scale to increase speed in issue solving and keeping the projects moving.

The tools allow testers to plan, create and organize test cases. Based on the project needs, test cases can be fully customized based on test requirements, titles, even test cases sequences can be created. The assignment is also possible.

At the execution level, with Zephyr, you can perform manual or automated tests. For manual tests, the software can update every step in the test case and include relevant information in those steps. Once finished, the test case can be saved and made available to all the users.

For automated tests, Zephyr can be integrated with automated testing tools with the use of ZBots and APIs, such as Jenkins, Selenium, eggplant Functional, etc.

What happens when you find a bug? Zephyr offers integration with either Bugzilla or JIRA bug-tracking tools. This functionality allows users to create bug reports and document any information related to the bug, without switching between programs.

Zephyr is good for companies with small and large testing teams due to easy implementation, user-friendly interface, and easy navigation

Are you looking for a faster way to software testing?

Selenium is an open-source tool used for automation of the tests performed on the web browser. Be careful though, Selenium can test only web applications. Testing desktop application or mobile application is not possible.

Why makes Selenium so good for testing dynamic web applications? There are a few reasons why software testers use this tool. Selenium allows test scripts to be written in many programming languages like Java, PHP, Python, Ruby, .Net, etc. Test cases can be carried out in Windows, Linux or Max operating systems and any browser can be used, Google Chrome, Mozilla, Safari, Opera and even Internet Explorer. To manage test cases or generating reports, Selenium can be integrated with TestNG and Junit and for achieving Continuous Testing, integrate the tool with Jenkins, Docker, and Maven.

As we saw above, Selenium is a very flexible tool. What types of testing can be automated with Selenium?

• Performance testing
• Integration testing
• Compatibility testing
• System testing
• Regression testing
• End-top-end testing

Just to be clear, the automation testing tools are not meant to replace manual testing. Automation testing is used for processes that don’t have to involve human intervention.

For more reading on the tools we wrote about, please check:

Discussion (0)

Editor guide