This article is about the list of criteria for tools in test automation, the criteria catalogue, how it was validated and the results of this validation.
The article series “Tester Tea-Time” covers topics and issues that our testers face every day. This article is dealing with the issue of documentation in day-to-day project work.
Determining which criteria are relevant when selecting a test automation tool is the basic requirement in the development of a criteria catalogue
After the Angular team announced in April that it would stop development of its Protractor e2e testing framework at the end of 2022, many developers have been asking themselves what will happen next. Which test automation tool should be used? The market has a wide range of alternatives, some of which will be discussed in this article.
The QA Navigation Board [https://blogs.zeiss.com/digital-innovation/en/qa-navigation-board/] enables teams to make targeted and efficient decisions for every software project with regard to aspects of quality assurance, their order of priority and their implementation. We have created a short video tutorial to explain how it works.
“Tester Teatime” is a blog post format, which addresses topics that testers deal with on a daily basis. The second part of this blog format deals with the questions: What is the connection of spelling and software development and which impact have spelling errors on the usability of an application?
This blog post addresses the high standards of security and compliance that we have to meet in every software project. Trained security engineers are responsible for ensuring that we achieve this within any given project. An especially persistent challenge they face is dealing with the countless dependencies present in software projects, and getting them – and their variety of versions – under control.
One of the first steps in introducing a test automation strategy is to evaluate suitable test automation tools. Since each project is unique, both the requirements and the choice of tools vary. This blog series is intended to provide guidance in selecting the appropriate solution.
“Historical software growth” is often used as an argument when a deviation is found in a piece of software that cannot or should not be corrected immediately. This article shows what this saying actually means and how it can be dealt with professionally and effectively in a project.
In this article we take a look at our latest ZDI online campus event for internal training, where our colleagues held a Remote Mob-Testing Workshop. We present our experiences on that and give some best practices.