Software testing manual testing tutorials and videos

Test Automation from the Manual QA Engineer Side

Software Testing Magazine — Fri, 22 Apr 2022 15:36:21 +0000

Many manual testers have a wrong idea about the basics of test automation, as a result, they draw false conclusions. In the following article, we will take a look at the top 5 questions about what test automation is and why switching to it is a must-have! Author: Nataliia Syvynska, TestMatick, https://testmatick.com/ Why Should Something Be Automated if QA Engineers Can Do It Manually? Of course, there are at least three factors to consider before you start implementing automation on a project: What is the project duration, what is its current scope, and how much it can be changed; Analyze how costly it will be to develop automated tests for a particular case. Sometimes, it is more difficult to automate tests than to execute them manually; Automated tests aren’t a good option if the system structure is completely changed on a project. However, if the project is running consistently, involves more and more staff and new functionality is added to it, the test can and have to be automated. In this case, all developed automated tests can become a kind of guarantee that nothing fails, while the programmers are developing new functionality. Of course, manual regression tests are great, but they are inextricably linked with the human factor, the tunnel vision, and unpredictability of places where bugs can be found. And at the same time, no one completely rejects manual checks because the need to check the functionality, which can be updated in a while, will not go anywhere! Is It Possible [...]

The post Test Automation from the Manual QA Engineer Side first appeared on Software Testing Magazine.

A Strategy for Browser Compatibility Testing

Software Testing Magazine — Tue, 12 Sep 2017 08:50:43 +0000

With the multiplication of versions, platforms (desktop, mobile, tablets) and operating systems, testing an application that is supposed to run in a browser is not easy. In this article, Alexander Rayskiy proposes an approach to select the set of browsers that will be used during the software testing activities. Author: Alexander Rayskiy, XB Software, https://xbsoftware.com/ It is hard to imagine a software quality team which is not constrained by time and resources and can test the web application in all available browsers. Thus, you need in the algorithm that allows determining the optimal set of browsers. The features of page rendering can change from browser to browser, which doesn’t allow to completely rely on testing automation and to get rid of the need to check manually how your app looks in different environments. In this situation, manual testing is a must. How to Choose the Right Browser There are different approaches to the browsers selection process. You can rely on the statistics of the browser usage among your target audience to define which one of them should be included in your list. It guarantees that your users will get the expected experience using your web application. Another approach is aimed at finding bugs. It implies testing on the browsers that cause the greatest number of problems such as the native Android browser, for example. Unlike the first case, these browsers are not used widely enough. But they can give you the understanding of how your app behaves in different usage [...]

The post A Strategy for Browser Compatibility Testing first appeared on Software Testing Magazine.

Moving from Manual to Automated Testing

Software Testing Magazine — Tue, 30 May 2017 15:20:31 +0000

Moving from manual to automated testing at a small company takes curiosity, research, careful planning and the ability to evolve as you learn. This talk will focus on how to get started, cultural hurdles, technology options, implementation and evolution. Additionally, virtualization and test case management will be covered. The goal for this topic is to show how to go from manual test case execution to an automated framework that can be built upon. https://www.youtube.com/watch?v=EUDKzhx3kY0 Video producer: http://seleniumconf.co.uk/

The post Moving from Manual to Automated Testing first appeared on Software Testing Magazine.

Why Building Record/Playback Testing Tools Is Hard

Software Testing Magazine — Wed, 14 Sep 2016 14:05:31 +0000

Almost every manual QA started with Selenium IDE or at least tried it at some point, and the retention rate is close to 0. This talk depicts the challenges that Test Automation Developers face. We categorize the challenges, name them, and see the skill set required to overcome the difficulties. The presentation compares the different record/playback tools and explains where they excel, and where we must resort to traditional solutions, e.g. generic programming languages and the Page Object design. This talk also discusses topics such as re-use of code, component isolation, separation of concerns, APIs, as well as where test fragility stems from and how to overcome it. Video producer: http://seleniumconf.org/

The post Why Building Record/Playback Testing Tools Is Hard first appeared on Software Testing Magazine.

Integrate Manual and Automated Testing in a Test Plan

Software Testing Magazine — Mon, 04 Apr 2016 14:03:11 +0000

The debate is always active in the software testing community about the usage of manual or automated testing. In this article, Art Trevethan explains that both have their value. He guides you on how to choose the test items to automate and proposes an approach to integrate test automation smoothly in your test plans without abandoning the benefits of manual testing. Author: Art Trevethan, Inflectra, https://www.inflectra.com/ Boil the ocean, eat the elephant, climb the mountain – all things we must do bit by bit, bite by bite, step by step. Developing a comprehensive application test plan can have the same overwhelming aspect – the task appears to be just too huge. The average test plan for a commercial grade application will have between 2,000 and 10,000 test cases. Your test team of five must manually execute and document results for between 400 and 2,000 test cases. And the scheduled release date of your product is fast approaching. No worries; clone your team and work around the clock. Or perhaps there’s a better way. As the graph above illustrates, there is an upfront cost to automated testing (as opposed to purely manual testing), but as the number of test cases and builds increases, the cost per test decreases. Coexistence – Manual and Automated Testing in the Same Test Plan This might be a good time to add automated testing to your test plan. The first step in this direction is realizing that no test plan can be executed completely with automated [...]

The post Integrate Manual and Automated Testing in a Test Plan first appeared on Software Testing Magazine.