Why should you use UI tests? How did we install automated tests in our infrastructure? Where were the hurdles and how did we solve them? We’ll try to answer all of these questions in this blog post.
UI tests – The solution to all problems
Tag Archives: testing
An Introduction to Testing Web Services with Karate and JUnit
Karate is a new test framework based on the well-known Cucumber library. It allows you to quickly write meaningful tests for web services using a domain-based language (DSL). Here is an example to help you get started with Karate.
Reasons why you as customer should test your new software intensively and at an early stage
The core of agile software development according to Scrum is regularly releasing product increments to the customer. The software’s functions are gradually extended, but the customer receives a version of their software right after the first sprint. That’s why at the end of each sprint, a review meeting is held where the development team presents the new functions to the customer. In this article, we will explain why it makes sense for the customer to participate in the reviews and why they should test the software created for them intensively and at an early stage.
Five Second Tests: Measure Content Usability and Get a First Impression in Five Seconds
A usability test, that only takes five seconds? Admittedly, it is almost too good to be true. The reservation against Five Second Tests, a specific form of remote usability testing, is great by and large. Experts traditionally place a lot of value on a clean methodology and clean results. Skepticism toward a new and simpler method is understandable. The attractiveness of Five Second Tests lies undisputedly in its simplicity. Through a link, participants are referred to a page on which they are shown a screenshot of a web site for exactly five seconds. Following, they have to answer questions to this page. Finished.
Quality assurance: Automated front end tests with Selenium IDE
A form that issues an error message after completing is an annoyance for the user and doesn’t generate any requests. Or: An interactive feature suddenly no longer functions after maintenance work on the code. These and similar scenarios are well-known to web developers. Therefore, it is indispensable for solid high-quality web applications, to run an acceptance test on a regular basis and make use of systematic bug tracking.
