Skip to main content

3 free tools for software test management

Today I want to take a look on the 3 freely available tools that allow for test management without breaking the bank those are good starting point for those who are looking for an alternative for high end tools like HP ALM and Smart Bear Test Complete.

Kiwi TCMS
This is a test case management tool that allow for proper test case creation and execution with nice reporting functionality. This tool does not contain internal bug tracking but integrates nicely with big players like BugZilla (A free Bug tracking tool)

TestLink
This is a full free solution for Software test management. It has it all from Requirement management to test case creation trough reporting and up to bug tracking. Everything can be done in this tool that has a lot of documentation online and a stable version the only downside is that its look and feel very outdated and might concern some modern testers out there

XStudio
This one is a commercial product that has a free, community, edition. It has a full spectrum of software development Life cycle components and can be a great starting point for a growing QA group. The free edition is limited to 200 test cases and MySQL database installation but for a fully professional free tool it a great starting point.

Conclusions

For those that are concentrating on the testing side only I would recommend the combination of Kiwi TCMS with Bugzilla as the go-to free solution and to those who require a free full-inclusive tool TestLink will be the thing. On the other hand if you are looking to potentially invest in a testing tool in the future but need a free fully functioning starting point you probably will choose the XStudio. It is true that all the big ones like offer the free trails and if you invest money you can go with them but keep in mind that the pricing point is completely different as well.

If you know of other free testing tools for manual test managment please write in the comments below.


Comments

Popular posts from this blog

Story Points estimation for Scrum with Fibonacci vs Shirt Sizes vs Linear - 7 minute guide

It is all began long time ago when Development Teams were constantly asked to provide estimate and they were having a hard time to properly face the task. Let's admit it, there are so many things that can change, happen, and simply go wrong during the development process that one can hardly expect a proper estimation of hours for each task. That why a relative estimation with Story Points came along.

Story Points Estimation
Its a different way to estimate the effort of the Scrum Development Team with-in Agile methodology, which means that instead of estimating hours of work the team estimates each effort relatively to other efforts in the project.
Let's assume that a developer knows that specific 'Task 1' is much harder than another 'Task 2' it is hard for him/her to quantify that harder feeling in hours of additional work but it is possible to say that it much more work. This situation is being address by Story Points when each story point is representing som…

7 Most Popular Test Types in Software Testing

Today we are going to return back to basics of software testing and discuss the 7 most popular test types that are being used in every software testing effort. Those different test types cover all the levels of the software to make sure that the final result matching the expectations from every possible angle. Here is our list: Unit testingSmoke testingRegression testingFunctional testingIntegration testingUser Acceptance TestingPerformance Testing


Now let’s have a deeper dive into each one of those by using a simple example of an imaginary system that was created in order to manage warehouse activity including shipments, inventory and goods receptions from suppliers.
Unit Testing This type of testing is usually performed by the developers and is covering the very basic development component. In this test developers are testing the straight forward functionality of a functional piece of code to make sure that it is performing according to their expectations. In our example: This test w…

What is the velocity of an Agile scrum methodology?

Let's discuss some of the important measurements in Agile, and that is the Velocity of the Scrum team work.
Based on Wikipedia definition Velocity is " ...the rate of change of its position with respect to a frame of reference and is a function of time...", which when transferred to the scrum world can be summarized as: The amount of work that the scrum team completed in a single measure of time - in a sprint.

How we Calculate Velocity?
Velocity is actually a very simple to calculate, it is done but totaling the number of story points of fully completed user stories from the sprint backlog. So if a current sprint included 4 user stories: 2 with 8 story points each, one with 3 story points and one with 32 story points. and by the end of the sprint the 32 one was not fully done the velocity calculation will be:
8+8+3=19
Note: the 32 story points are not part of the velocity calculation as this user story was not completed.

What Velocity is used for?
The velocity is used i…