If you work as a software quality assurance (QA) engineer, you have to deal with many documents that are not all produced during software testing activities. This article lists the documentation that is important for software QA engineers, like the product requirements document or the user guide.
Test management is defined by Wikipedia a part of the software testing process that includes the planning of tests and test cases, their execution and the storage and analysis of the tests results. This is achieved also by the integration with requirements management tools, functional software testing tools like Selenium or Cucumber, continuous integration tools like Jenkins or TeamCity, bug tracking tools like Bugzilla or Mantis, project management tools like Trello, Redmine or JIRA.
QuAck is a web-based open-source test management tool that can store test cases and test suites and execute them. It is based on a pluggable architecture that allows implementation of custom authentication providers, integration with tracking and test executing systems. This article presents the key features of QuAck.
Hardware-as-a-service (HaaS) allow using distinct hardware components through the Internet analogously to the cloud services. This article discusses the differences of the testing approaches that could be used to test hardware compared to software.
Every test suite has them: a few tests that usually pass but sometimes mysteriously fail when run on the same code. Since they can’t be reliably replicated, they can be difficult to fix. The good news for software testing is that there is a set of usual suspects that cause these issues: test order, async code, time, sorting and randomness.
Since the start of software development, we have always had to test our software. And over the course of several decades, the discipline of software testing has seen many best practices and patterns developed. Unfortunately however, not all practices have been good and there are also anti-patterns.
Your team has some test data. Let’s say you loaded in a backup form production a few months ago. Your QA specialists are familiar with the data, but your software developers hate it. They keep telling you, “It is not the right data,” or, “It is not very useful for testing.” You let them write and automate some tests, but it is not enough.