Tutorials and resources on how to apply test automation in software testing
Your Internet of Things (IoT) solution is unique and you will quickly realize that testing end-to-end IoT performance is hard. This article explains what you should require in an IoT performance testing tool to solve these problems.
According to the Norwegian Anti-Discrimination and Accessibility Act all new websites in Norway should be universally designed. Existing websites needs to be universally designed from 2021. To ignore this or postpone the subject until late in the development process can not only be expensive but will often result in sub-optimal solutions.
pCloudy is a cloud based continuous testing platform designed to enhance the quality of the mobile application under test. In this white paper, we will discuss how we can increase the speed of testing mobile apps by enabling continuous testing. We will have an overview of how we can perform manual and automation testing and list the latest features of pCloudy at the end.
The purpose of this article to share thoughts about software testing activities in the Scrum Agile framework. This article is divided in two main parts. The first part focuses on explaining the Scrum approach, who are the players, how are the plans transformed into actions, key ceremonies and what happens in a Scrum sprint. In the second part, I describe the software testing process followed in Scrum methodology and how it can be integrated within Scrum sprint.
“Tools and machines are great, but in the end, it is the people who matter. Putting together an effective automated test team requires lots of planning and skills.” This might the emblematic quote of this great book about software testing automation. The book groups case studies written each by a different author. Each case study is presented in the preface, so you can pick the story that you prefer, based on many criteria like application domain, tool type… or if the project was successful or not.
You all know Selenium tests are flaky by nature, slow to run, expensive to maintain and finding the root cause of a failure is not always easy. This presentation shows you how to shift your UI tests left with an Agile testing approach.
You have inherited some legacy C++ code: it is valuable, but it doesn’t have tests, and it wasn’t designed to be testable, so you need to start refactoring. But you can’t refactor safely until the code has tests, and you can’t add tests without refactoring! How can you ever break out of this loop?
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates