Software testing exploratory testing tutorials and videos

Exploratory Testing Chrome Extensions

Software Testing Magazine — Mon, 05 Aug 2024 12:00:20 +0000

This article presents a list of exploratory testing extensions available for the dominant Chrome browser. The current trend in software testing might be to talk about test automation or artificial intelligence, but in some cases nothing replace the intelligence of a human tester to detect bugs and consequences of irrational user behavior. Wikipedia defines exploratory testing as “an approach to software testing that is concisely described as simultaneous learning, test design and test execution. […] While the software is being tested, the tester learns things that together with experience and creativity generates new good tests to run.” This article present a list of exploratory testing extensions available on the Chrome Web Store as it is currently the browser with the larger market share. The main features you can expect from an exploratory testing tool are: * Easy access to the tool features from a toolbar icon * Start and stop exploratory testing sessions * Taking notes while exploring a web application for test * Classifying your notes in different categories (questions, bugs, …) * Taking screenshots and / or screen recordings * Automatic recording of application information like url, page title, etc. * Produce and save session reports in html or pdf formats Some vendors’ tools will also allow sharing data with test management platforms, but they can also work as a standalone solution with more limited features. We list here only Chrome extensions that can work without being connected to another tool. Updates August 5 2024 * added AIFEX [...]

The post Exploratory Testing Chrome Extensions first appeared on Software Testing Magazine.

‘early Model Based testing’ (eMBT) – Part 2

Software Testing Magazine — Tue, 31 May 2022 13:47:44 +0000

‘early Model Based Testing’ (eMBT) is a software testing approach that aims to optimize the test case design phase. The first part of this article presented the exploring and review phase of this approach. This article presents the generation of test cases from the model and their execution. Author: Silvio Cacace, TestCompass, www.compass-testservices.com 3. Coverage phase When the test model is made, discussed and assessed by the whole team, the test cases can then be automatically generated, based on the agreed test coverage. The agreed test coverage can be the result of a previously performed product risk analysis where the various functionalities are categorized according to priority. Or on an ad hoc risk analysis, performed in collaboration with the business. In the eMBT tool it is possible to generate the test cases automatically, based on a pre-selected test coverage form, from weak to strong. The following test coverage forms are available. Node coverage All nodes in the model will be tested at least once. The Action/State, Decision and Result symbols are classified as nodes. Edge coverage All edges in the model will be tested at least once. The Yes- and No-path links out of the Decision node are classified as edges. Multiple condition coverage All multiple conditions will be tested at least once. A multiple condition is a combination of 2 consecutive test paths (Yes- and No-path out of a decision). Path coverage All possible paths from Start to End will be tested. After the agreed test coverage is selected, [...]

The post ‘early Model Based testing’ (eMBT) – Part 2 first appeared on Software Testing Magazine.

‘early Model Based testing’ (eMBT) – An early model based exploratory testing approach in practice

Software Testing Magazine — Mon, 23 May 2022 15:21:09 +0000

‘early Model Based Testing’ (eMBT) is a software testing approach that aims to optimize the test case design phase. This is achieved by stimulating communication and collaboration between all project stakeholders to get early feedback and a shared understanding of the requirements in an early stage of the software development life cycle. Author: Silvio Cacace, TestCompass, www.compass-testservices.com “That looks very nice and it works fine. But sorry, it’s actually not what we wanted” Do you recognize this? Off course, you want to prevent this, because it indicates that you have delivered a product that might look nice and works fine but is not in accordance with the customers wishes. Still 35% of all bugs in production can be traced back to the requirements. And these bugs are almost always related to poorly defined requirements or a lack of understanding around those requirements. To make sure we meet the customer’s needs (business value), we need to achieve a shared clear understanding of the complete set of requirements. In addition, requirements change continuously, and it is therefore important to manage these changes effectively. ‘early Model Based Testing’ (eMBT) is a solid approach to solving these problems and challenges. ‘early Model Based Testing’ (eMBT) ‘early Model Based Testing’ (eMBT) is a software testing approach to ensures the optimization of the test case design phase. But more importantly, eMBT stimulates communication and collaboration between all stakeholders (business and technical stakeholders) with the aim of getting early feedback and a shared understanding of the requirements [...]

The post ‘early Model Based testing’ (eMBT) – An early model based exploratory testing approach in practice first appeared on Software Testing Magazine.

Improve Exploratory Testing with Creativity

Software Testing Magazine — Tue, 23 Feb 2021 18:02:17 +0000

This video explains how to improve your exploratory testing through LESS preparation but more creativity! One of the characteristics of exploratory testing is that you do less preparation and that you decide on the spot what your next test case will be. To be able to do this you should have creative skills. But how do you become more creative? How can you train this? In this video, Jan Jaap Cannegieter tells how he became more creative. He shares some concrete things you can do to train your creativity and share some tools you can use during exploratory testing sessions. Video producer: http://www.pnsqc.org/

The post Improve Exploratory Testing with Creativity first appeared on Software Testing Magazine.

Teaching and Coaching Exploratory Testing

Software Testing Magazine — Mon, 06 May 2019 14:35:34 +0000

There is a lot of talk around software testing - who will do it, when it needs to happen, boxes it needs to fit in — yet not enough on the actual testing. This webinar explores one problem in a demo setting using an exploratory testing approach. This means live testing (and live coding) to figure out the options to get a test program covered – for code coverage, for spec coverage and for risk coverage. Video producer: http://www.associationforsoftwaretesting.org/

The post Teaching and Coaching Exploratory Testing first appeared on Software Testing Magazine.

Exploratory Testing Basics, Experiences & Future

Software Testing Magazine — Thu, 21 Dec 2017 15:30:12 +0000

James Bach defines Exploratory Testing as “simultaneous learning, test design, and test execution. In other words, exploratory testing is any testing to the extent that the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests.” In this video, Kari Kakkonen talks about exploratory testing basics, experiences and future. You will find out where exploratory testing is the most useful, how to develop one’s learning and thinking skills to enable exploratory testing, etc. https://www.youtube.com/watch?v=xH5rFe8vHAs Video producer: http://testconf.ru/?lang=en Further reading: Exploratory Testing: Finding the Music of Software Investigation

The post Exploratory Testing Basics, Experiences & Future first appeared on Software Testing Magazine.

Debriefing Exploratory Testing Session Notes

Software Testing Magazine — Thu, 23 Mar 2017 18:22:04 +0000

Session notes that you use when you adopt an exploratory testing approach can be used to capture more than bugs. They not only serve as a memory of a bug, but a structured testing and learning method can be deduced from the session notes. This presentation discusses: * Introduction to exploratory testing and session based test management * Elements of Session Notes * Note taking skills, tools and tips * Detection theory, Metrics * Many complain about exploratory testing being unstructured, session notes is an answer to such misleading beliefs. Video producer: http://seleniumconf.in/ Further reading: * What is Exploratory Testing? * Exploratory Testing: Finding the Music of Software Investigation

The post Debriefing Exploratory Testing Session Notes first appeared on Software Testing Magazine.

Oblique Testing

Software Testing Magazine — Wed, 21 Sep 2016 14:24:16 +0000

In theory, we can consider software testing as a very rationale approach. You start from unit of code or requirements and then you create the tests that will prove that your software does what it is expected to do… and doesn’t create problems with edge cases. In his book Oblique Testing, Mike Talks propose to add an additional perspective to software testing using the oblique strategies approach. The oblique strategies is a set of card originally used by music producer Brian Eno to make recording artists try something new. This book adapts this approach to the software testing world by providing a set of cards. Based on fictional bad reviews for apps., they are mainly focused on the testing of a mobile app, but they are generic enough to be applied to other contexts where you have many customers using your software. The book provides also some suggestions on how to apply this approach in Agile and traditional software development projects. Oblique Testing is an original approach to perform some exploratory testing where the full project team is involved and not only the software testers. I will suggest to read this very short book to every software tester or project manager that wants to introduce a different perspective in its software testing activities. Reference: Oblique Testing, Mike Talks, https://leanpub.com/obliquetesting Quotes As I mentioned before, when we are testing, we’re using our imagination to work out “ways the software could go wrong”. The most annoying bugs are the ones which get [...]

The post Oblique Testing first appeared on Software Testing Magazine.