Software Testing is hard. Realistic testing of web applications in a real browser is even harder. In this video, Gleb Bahmutov shows you how to quickly test any web application using cutting-edge tools. Then you will see how to build high-quality software from individual modules using appropriate tools and creating an environment where bugs can be discovered immediately and fixed quickly.
Your team has some test data. Let’s say you loaded in a backup form production a few months ago. Your QA specialists are familiar with the data, but your software developers hate it. They keep telling you, “It is not the right data,” or, “It is not very useful for testing.” You let them write and automate some tests, but it is not enough.
If you are in bed with your partner but you are not collaborating, then nothing good is going to happen. This is thee same for quality assurance (QA) and software testing in Agile development projects.
Most of the time, software testing is based on comparing the actual behavior of a code or a system with its expected behavior. In his article “The Challenges of Testing in a Non-Deterministic World”, Donald Firesmith explains however that not all software and systems are deterministic, for instance an autonomous adaptive vehicle that uses machine learning software, and that software testing needs to adapt to this context.
This talk discusses elastic leadership principles in the context of software testing. You will learn how to apply them effectively in your day to day work and how they can help you as a software tester to become more effective, while making others around you more effective as well.
In his preface of the book “Common System and Software Testing Pitfalls”, Donald G. Firesmith writes “You can think of this book as a catalog and repository of testing antipatterns: the pitfalls to avoid, how to mitigate their negative consequences if you can’t avoid them, and how to escape from them once you’ve fallen in. Like a naturalist’s field guide to wild animals, let this be your guidebook to the dangerous world of testing mistakes and its denizens – the many creative ways people have discovered to botch testing.”
What kind of software testing do we need to have in a continuous deployment pipeline? What does it take to push a commit all the way to deployment? Fully automated. Several times a day. This is how Spotify does it.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates