SQA Day: A Day to Learn, Network, and Grow
In everyday life, we are dependent on several applications to make our daily lives easier. For example, we use software to order food, buy everyday goods, connect with family and friends, transfer money when necessary, and plan transportation using services. The software provides all of these benefits. However, if this software does not function properly, it may complicate our daily lives. Behind the scenes, hidden soldiers put in a lot of effort to ensure the software we use daily functions error-free and flawlessly.
Tester’s Day was created to honor and value their significant achievements. This post will explore the origins and meaning of Tester’s Day and honor the people essential to producing excellent software.
Learn Common Software Testing Mistakes and How to Avoid Them.
Story Behind SQA Day
September 9th is a special day to recognize software testers. It’s a day to acknowledge their work and ensure our software functions properly. This Day reminds us of an amusing tale from 1947, a natural bug ended up inside a computer! This is where the term “debugging” came from. As software has developed since then, testers have been crucial in making sure our software is reliable and usable.
The Celebration of Tester’s Day
Software companies and QA communities throughout the world celebrate Tester’s Day in a variety of ways to honor the dedication of testers. Here are a few typical ways that people celebrate it:
- Recognition and Awards: To appreciate the achievements and commitment of high-performing testers, companies frequently present them with awards, certificates or little presents.
- Team Celebrations: To honor their QA teams, many companies organize activities like coffee breaks, team lunches, or after-work get-togethers.
- Skill-Enhancing Activities: Some businesses use Tester’s Day to host training sessions, seminars or workshops to help testers pick up new abilities or testing methods.
- Social Media Shoutouts: Communities and organizations utilize online platforms to honor testers, tell their stories, and send messages of gratitude emphasizing the importance of QA specialists.
- Fun Testing Challenges: To remember the tester’s Day and showcase their abilities, many QA teams take part in enjoyable testing tasks or contests, such as bug hunts.
- Appreciation Messages: Managers and coworkers frequently send thank-you notes or cards to show their gratitude for testers’ hard work and commitment to excellence.
Tester’s Day’s Significance
Daniel Galin’s book Software Quality Assurance: From Theory to Implementation covers every aspect of Quality Assurance (QA), including the author’s inspiration. The importance of QA in producing reliable, high-quality software is highlighted in this book, which also covers key QA concepts and techniques. Here, you can see a glimpse of the book and its history.
When Colorado residents celebrated the opening of the new Denver International Airport (DIA) in February 1995, the information technology industry undoubtedly recognized the end of a horrific time. By 2020, DIA was supposed to be the biggest airport in the US, handling 110,000,000 passengers a year and 1750 flights a day via 200 gates and 12 runways.
The software-based baggage handling system’s failure caused DIA’s operations to be delayed by 16 months, resulting in an estimated $2 billion in losses. Also, compared to the initially intended system, the luggage handling system that was eventually put into use was significantly downscaled. The IT technology collapse at DIA was particularly distressing to the profession, whether because of the magnitude of the losses or because of the public interest and remarks it generated, even though more harmful software system failures have also been documented since 1995.
The author is one of many SQA professionals who think that if the project had been started with the right software quality assurance tools, a failure of this magnitude would not have happened, or, at the very least, the damages would have been significantly lower. The techniques and resources covered in this book, particularly the risk management protocols, may have recognized the seriousness of the problem very early on and allowed for the prompt implementation of the necessary corrective actions during the project. Other SQA tools might have guaranteed that the system would be completed on time and in complete accordance with its requirements. An acceptable degree of software quality can be attained, in accordance with the author’s conception of software quality assurance, by:
■ Combined application of a great variety of SQA components.
■ A particular focus on quality during the pre-project and early stages of software development.
■ Execution of detailed SQA procedures to regulate the quality of work performed by outside parties (subcontractors, vendors of repurposed software modules and commercial off-the-shelf software, and clients themselves when they do project components).
■ Assuming that functional requirements, schedules, and budget plans behave by the principle of communicating vessels—that is, a failure (or decreased level of achievement) in one of these three fluid components causes an immediate failure in the others—SQA activities can be added to project schedules and budget control.
This idea of software quality assurance serves as our roadmap for the entire book
Conclusion
Tester’s Day is a unique occasion to honor the dedication of software testers. They ensure the smooth functioning of our programs and apps. Let’s give them recognition for their work!
Happy Tester’s Day!!!
Reference Book: https://aagasc.edu.in/cs/books/Software%20Quality%20Assurance%20From%20Theory%20to%20Implementation.pdf
