Software testers are expected to come up with a lot of test artifacts during the process of software testing. The traditional test artifacts are time-intensive, bulky and their structure do not support the agile approach of software development. When working in an agile environment, software testers work in highly compressed test execution cycles.
It can be intimidating for inexperienced software development teams embarking on their test automation journey for an existing code base. There is so much to test, and so many ways to test. You can often see teams stuck with debating on where to start software testing and what tools to use and best practices:
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.