QA Bean

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 s...

I lately noticed that there is some confusion going on around the software testing in regards to user facing parts of the system. Testers mention that they are planning to “run some UI testing” or others speak about “strange UX on that system”. I would like to spent some time today and emphasizing the main 3 differences between UI and UX and how we are testing each one, and by whom. But let’s start from the beginning what is UI and what is UX? UI is a User Interface, usually referring to anything that can be visually seen by the user when interacting with the system. That will include colors, page design, logos, element shapes, etc. UX is a User eXperience, usually referring to anything that can be done by the user when interacting with the system. That will include what can be clicked, what can be done, what will be returned back to user and in what way, etc. With that understanding we can now define the 3 most important identification points for each one UI - User inte...

There are different approaches to achieve a proper Defect life-cycle solution with different theories and goals behind each one of them but from my experience most of the solutions that will have the following 10 statuses when implemented will have the better results in improving the final quality of the company’s product: