The importance of Agile Software Testing by Kudakwashe Siziva

From the beginning of time, the relationship between developers and software testers has always been that of 'Cat and Mouse'. This relationship has had its fair share of short comings which chiefly included unmet deadlines and lack of confidence when shipping software products. The talk is meant to introduce a better relationship between developers and testers by going over the importance of including testing in an Agile cycle.

We will look at different levels of testing E.g. Unit vs integration testing, how units work together. Knowing why we are writing each test - what are we trying to achieve when we write a test for a unit as that is a place that developers struggle and either write duplicate tests or not enough and changeability and confidence can suffer as a result.

Objective is to build better agile software teams and ship clean python projects with confidence.

Transcript

1. HELLO! I am Kudakwashe Siziva I am a web developer and software product manager at Muzinda Hub. I am here to share with you the benefits of Agile Software Testing.
2. Importance of Agile Software Testing
3. “I don’t care if it works on your machine! We are not shipping your machine!” — Vidiu Platon.”
4. BIG Problem EcoFarmer – Case Study
5. Defining Terms ü Agile ü Software Testing
6. Agile ü Is an umbrella term to describe of software development methods including scrum ü Emphasizes collaborative, integrated teams, frequent delivery and ability to adapt to changing business needs.
8. Software Testing ü Is a process of executing a program or application with the intent of finding the software bug. ü Is important to point out defects and errors made during development ü Makes sure of customer’s reliability and satisfaction in the application ü Helps ensure quality in product, quality product delivered helps in gaining customer confidence
10. Ultimate Solution üAgile Software Testing
12. Principles of Agile Software Testing ü Testing moves the project forward ü Testing is not a phase ü Everybody tests ü Reduce feedback latency ü Tests represents Expectation ü Bugs do not hang around ü Reduce test documentation overhead ü Tested is part of “done” ü From test last to test-driven
13. THANKS! Any questions? You can find me at: Github: kaysiz · Twitter: brysiz· ksiziva@gmail.com
14. Credits Special thanks to all the people who helped me: › Yollanda Gonyora › Patrick Vine