Tutorials and resources on how to apply test automation in software testing
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 (with the Gerkhin language), continuous integration tools like Jenkins or TeamCity, bug tracking tools like Bugzilla or Mantis, project management tools like Trello, Redmine or JIRA.
The challenges faced by QA teams can lead to delays and missed issues in software development. But AI-powered test management tools provide a way of improving efficiency, visibility, and overall software quality.
The software development trend that shifts the target platform from the desktop to web, cloud and mobile applications has fostered the development of load testing services and performance testing tools on the web. It is an obvious option to use web-based and cloud-based load testing tools for applications that can be accessed by web users. This article presents the free offers from commercial web load testing services providers.
Running automated tests is a good thing for software quality assurance. Test reporting tools help you understand the results of the current test run. You could also be interested to see how your tests results evolve over time. Here are some open source tools to help you do this, as they produce meaningful tests reports and dashboard.
Regression testing is a key practice to prevent changes for bringing negative side-effects in production. Running them could however take a long time and slow delivery of new code. This article introduces change-to-test mapping for regression testing. It is an approach that aims to run only the tests that truly matter, without compromising test coverage.
In a lot of software development teams, test automation code is treated much less carefully than production code. It is expected to just work. Mindless copy and paste of setup code from one test case to another is seldom seen as problematic, scripts duplications are widely accepted, and things are named randomly.
Bugs, issue, defect, there are many names to define the problems you have with software, either during the code development phase or when the application is already in production. Bug tracking tools are an integrated part of a software quality and software testing strategy and there are many open source tools available.
