Quality Assurance Image Library
Check out the growing QA Image Library. This is my personal colleciton of Slack Images for that perfect QA Moment.
Winter Rules Are In Effect
Just like in golf, where winter rules adapt the game to colder, more challenging conditions, the world of Software Quality Assurance (QA) often requires its own set of "winter rules" to navigate the complex landscape of testing during the colder months. Let's tee off and explore some essential tips and strategies to keep in mind for QA this winter.
1. Embrace AI and Machine Learning: Your Caddies in the Snow With the landscape of software development continually evolving, AI and machine learning have become crucial allies, much like a caddy in a snow-covered golf course. They assist in automating test case generation and optimizing test coverage, ensuring that your QA process doesn't freeze over in the winter chill. Like a caddy predicting a tricky terrain, AI algorithms can predict potential defects, making your testing process more efficient.
2. Continuous Testing: Keeping the Game Moving Just as a golfer wouldn't stop after a single hole, continuous testing ensures that QA is an ongoing process. With the adoption of DevOps and CI/CD practices, tests are automated throughout the development pipeline. This approach helps to keep the game moving, identifying issues early and reducing the time and cost associated with fixing bugs.
3. Shift-Left Testing: Clearing the Snow Early In golf, it's always best to avoid hazards, and in QA, shift-left testing does just that. By moving testing activities earlier in the development cycle, defects are caught at their source. Think of it as clearing the snow from the fairway early on, ensuring a smoother play throughout.
4. Quantum Computing Testing: New Clubs in the Bag Quantum computing is like a new set of golf clubs ? it offers great potential but requires a different approach. The unique challenges of quantum software require innovative testing strategies. This winter, be prepared to add these new "clubs" to your QA "golf bag."
5. IoT and Embedded Systems Testing: Playing on a New Course Testing IoT devices is akin to playing on a new, unfamiliar golf course. It demands understanding the unique challenges of diverse environments and ensuring secure communication, much like adapting to different course layouts and hazards.
6. Data Quality: The Scorecard of Your Game In QA, data quality is your scorecard. It's vital to ensure that the data is accurate, complete, and reliable. This winter, focus on maintaining a clean scorecard by integrating comprehensive data quality checks into your QA process.
7. Mobile Testing: Navigating the Bunkers Mobile app testing is as crucial as navigating the bunkers in golf. It's about ensuring that the apps perform well, are user-friendly, and are secure across various devices ? much like a golfer mastering different bunker shots.
8. Cybersecurity: Guarding Against the Unexpected Hazards Cybersecurity in QA is like being prepared for unexpected hazards on a golf course. Regular security testing, including ethical hacking and penetration testing, ensures that your software is fortified against unforeseen risks.
9. Exploratory Testing: The Creative Play Finally, exploratory testing in QA is the equivalent of a creative play in golf. It's about using intuition and experience to explore and identify issues that scripted testing might miss ? much like a golfer taking a create shot for the green despite challenging conditions.
Conclusion: Keeping Your Game Sharp in the QA Winter As the winter sets in, it's crucial for QA professionals to adapt their strategies, much like golfers adjust their game to the seasonal changes. By embracing these winter rules ? from leveraging AI and ML, engaging in continuous and shift-left testing, to focusing on data quality and cybersecurity ? you can ensure that your software testing process remains robust and efficient, even in the frostiest of conditions.
Remember, in the world of software QA, every season brings its own challenges and opportunities. This winter, stay ahead of the game by being adaptable, innovative, and vigilant. Happy testing, and may your metaphorical drives land on the fairway and your code be bug-free!
Setting Productive QA Resolutions for 2024
As we step into 2024, it's essential for Quality Assurance (QA) professionals to set resolutions that not only enhance our skills but also align with the evolving landscape of software testing. With a decade of experience in QA, I've witnessed how automation has revolutionized our field. This year, let's focus on setting resolutions that embrace reliable automation, ensuring our work is more efficient, accurate, and impactful.
Resolution 1: Mastering Advanced Automation Tools
Goal: Expand your toolkit by mastering one or two advanced automation tools.
Why It's Important: Automation tools are constantly evolving. Staying updated with the latest advancements is crucial for maintaining an edge in the QA field.
How to Achieve It: 1. Identify tools that are gaining traction in the industry, such as AI-driven testing frameworks. 2. Allocate regular time slots each week for learning and experimentation. 3. Join webinars, online courses, or workshops to gain practical knowledge.
Resolution 2: Integrating AI and ML in Test Automation
Goal: Incorporate AI and ML algorithms to improve test efficiency and accuracy.
Why It's Important: AI and ML can significantly reduce the time spent on test case maintenance and can identify patterns in data that humans might overlook.
How to Achieve It: 1. Start with basic AI/ML models relevant to testing scenarios. 2. Collaborate with AI experts or take up courses to understand the fundamentals. 3. Implement AI/ML in areas like test case generation, anomaly detection, and predictive analysis.
Resolution 3: Focusing on Test Data Management
Goal: Improve the management and utilization of test data.
Why It's Important: Quality test data is crucial for effective automation. Poorly managed data can lead to inaccurate testing results.
How to Achieve It: 1. Utilize tools for test data generation and management. 2. Regularly update and cleanse your test data repository. 3. Explore data anonymization methods to ensure data privacy.
Resolution 4: Emphasizing on Continuous Testing in DevOps
Goal: Implement or enhance continuous testing practices in the DevOps pipeline.
Why It's Important: Continuous testing ensures that any code changes are immediately tested, reducing the chances of bugs in production.
How to Achieve It: 1. Collaborate with development teams to integrate testing into the CI/CD pipeline. 2. Automate regression and integration tests to run with every build. 3. Monitor test results and feedback for continuous improvement.
Resolution 5: Prioritizing Non-Functional Testing Automation
Goal: Increase the focus on automating non-functional testing like performance, security, and usability testing.
Why It's Important: Non-functional aspects are as critical as functional features for the success of a software application.
How to Achieve It: 1. Identify key non-functional areas relevant to your projects. 2. Use specialized tools for automating tests like load testing, security audits, etc. 3. Incorporate non-functional testing early and regularly in the development cycle.
Conclusion
Setting and following through with these QA resolutions will not only enhance your skill set but also significantly improve the quality and reliability of the software you test. Automation is the key to future-proofing your QA career, and by embracing these resolutions, you're well on your way to a productive and innovative 2024 in the realm of software testing.
Precision Scheduled Railroading
Precision Scheduled Railroading (PSR) is a methodology that revolutionized the railroad industry by streamlining operations, improving efficiency, and reducing waste. Its core principles can be intriguingly applied to the field of Software Quality Assurance (QA) Testing. Here's how we can draw parallels between PSR and QA practices in software development:
Introduction to Precision Scheduled Railroading (PSR)
PSR is a logistics philosophy focused on improving efficiency and resource utilization in railroad operations. It involves strict scheduling, minimizing layovers, and optimizing routes. The goal is to deliver better service with fewer resources and reduced operational complexity.
Applying PSR Principles to Software QA Testing
1. Strict Scheduling in Testing:
- PSR Parallel: Like PSR's rigorous train schedules, QA teams can implement strict testing schedules.
- Application: This involves timely execution of test plans and adhering to release cycles. The goal is to reduce waiting time (idle resources) and ensure timely delivery.
2. Resource Optimization:
- PSR Parallel: PSR minimizes resource wastage by optimizing asset use.
- Application: In QA, this translates to efficient use of testing tools, environments, and personnel. Leveraging automation where appropriate can significantly enhance this aspect.
3. Minimizing Layovers (Downtime):
- PSR Parallel: Reducing idle time for trains.
- Application: In QA, this means minimizing downtime between test cycles and ensuring continuous testing and integration. This approach helps in early identification and resolution of defects.
4. Route Optimization:
- PSR Parallel: Optimizing train routes for maximum efficiency.
- Application: For QA, this involves planning test cases and paths that cover the most critical functionalities with minimal redundancy. It's about finding the most efficient path to cover all test scenarios.
5. Adaptive and Predictive Planning:
- PSR Parallel: PSR requires adaptive planning to respond to dynamic conditions.
- Application: QA teams must adapt their testing strategies based on real-time feedback and predictive analytics to anticipate potential issues.
6. Quality Over Quantity:
- PSR Parallel: Focuses on the quality of rail services rather than the quantity.
- Application: In QA, this emphasizes the importance of thorough, high-quality testing over simply increasing the number of test cases or test executions.
7. Stakeholder Communication and Transparency:
- PSR Parallel: Effective communication is key in PSR for smooth operations.
- Application: Regular updates and transparent communication with stakeholders (developers, project managers, clients) are crucial in QA for ensuring everyone is aligned on the quality goals and outcomes.
Conclusion: A New Paradigm for QA
Adopting PSR principles in Software QA Testing can lead to more efficient, effective, and lean testing processes. This approach encourages QA professionals to think strategically, optimize resources, and focus on delivering the highest quality software in the most efficient manner possible. As the software industry continues to evolve, integrating such innovative methodologies from other industries can provide a competitive edge and lead to superior software products.
Top 5 QA Blog Posts of 2023
As a Quality Assurance professional with a decade of experience in software testing, I've had the privilege of sharing my insights and experiences through our weekly QA blog. This year, we've covered a multitude of topics, each offering unique perspectives and valuable lessons in the realm of software testing. As we close out the year, let's revisit the top 5 blog posts that resonated most with our readers.
1. Stealth Mode Deployment vs Release Canaries: A Strategic Duel
Perhaps the most debated topic of the year, this post explored the contrasting deployment strategies of Stealth Mode and Release Canaries. Stealth Mode Deployment, characterized by its low-key, gradual rollout, offers the advantage of minimal disruption. On the other hand, Release Canaries involve deploying new features to a small, controlled group to gauge reaction and catch issues early. This post was a deep dive into when and how to use each strategy effectively.
2. Test Entrance Criteria: Setting the Stage for Success
This post emphasized the crucial step of establishing clear Test Entrance Criteria before diving into the testing phase. By outlining the necessary conditions, such as environment setup, resource allocation, and documentation completeness, this post guided QA professionals on how to set a solid foundation for successful testing outcomes.
3. QA and Minutemen: Rapid Response in Testing
Drawing an analogy between QA professionals and the historical Minutemen, this entry highlighted the importance of agility and rapid response in software testing. In an era where technology evolves rapidly, the ability to quickly adapt and respond to new challenges is invaluable. This post provided strategies for developing such skills and emphasized the importance of proactive planning.
4. Too Many Cooks in the Kitchen: Navigating Team Dynamics in QA
A favorite among readers, this post tackled the complexities of team dynamics in QA environments. Using the adage "too many cooks spoil the broth," it discussed how too many inputs or conflicting directions can hamper the efficiency and effectiveness of QA processes. The post provided insights on how to manage large teams and ensure cohesive, streamlined testing processes.
5. The Russian Proverb and its Relation to Software Quality Assurance Testing in 2023
This intriguing post drew parallels between a traditional Russian proverb and modern QA practices. It discussed how timeless wisdom applies to contemporary software testing, emphasizing thoroughness, attention to detail, and the importance of not rushing the testing process. This post was a reminder of how cultural insights can enrich our approach to software quality assurance.
As we look forward to 2024, I am excited to continue exploring the ever-evolving landscape of QA and sharing insights that can benefit our community. The world of software testing is dynamic, and there's always more to learn and share. Here's to another year of engaging topics, thoughtful discussions, and excellent quality assurance practices!
Diderot Effect
The Diderot Effect is a phenomenon named after the French philosopher Denis Diderot, who described the impact of a single new possession on the rest of one's belongings. The idea is that acquiring a new item can lead to a chain reaction of purchases as we try to bring everything else up to the same standard. This effect can be observed in many aspects of our lives, including software quality assurance testing.
Software testing is the process of evaluating a system or application to identify defects and ensure that it meets specified requirements. It is an essential part of the software development lifecycle that helps to improve the quality of software products. However, the Diderot Effect can impact the effectiveness of software testing by leading to an over-reliance on tools and techniques that are not always necessary.
For example, a team of software testers may acquire a new testing tool that promises to improve their testing efficiency. However, this new tool may require additional resources to operate effectively, such as training, support, or even more powerful hardware. As a result, the team may start to invest more and more time and resources into the tool, neglecting other important aspects of their testing process.
The Diderot Effect can also lead to a situation where testers become overly reliant on automated testing tools, such as regression testing tools, without considering other testing methods. Automated testing can be very efficient, but it is not always the most appropriate approach. Some types of testing, such as usability testing or exploratory testing, require human input and observation to identify issues that automated tools may miss.
To avoid the negative effects of the Diderot Effect on software quality assurance testing, it is important to focus on the overall testing process and not just individual tools or techniques. A well-designed testing strategy should consider the strengths and weaknesses of each testing method and tool and use them in a complementary way. This approach will ensure that the testing process remains efficient, effective, and flexible, adapting to the changing needs of the software development lifecycle.
In conclusion, the Diderot Effect is a real phenomenon that can impact the quality of software assurance testing. By being aware of its effects and focusing on a holistic approach to software testing, testers can ensure that they are using the most appropriate tools and techniques for their specific needs, without sacrificing other important aspects of the testing process.
Making Evidence Base Decisions
In my decade-long journey as a Quality Assurance (QA) professional, I've witnessed the transformative power of evidence-based decisions in software testing. This approach not only enhances the quality and reliability of software but also aligns perfectly with the strategic goals of an organization. In this blog, I'll dive into the nuances of making evidence-based decisions, focusing on long-term testing strategy and the implementation of automation, ensuring these solutions realistically fit into a company's deployment strategy.
Understanding Evidence-Based Decisions in QA
Evidence-based decision-making in QA involves using data and facts to guide testing processes and strategies. It's about moving away from assumptions and gut feelings to a more structured approach that leverages metrics, test results, and historical data.
Key Benefits:
- Improved Test Accuracy: Data-driven insights lead to more accurate testing, identifying real user scenarios and bug patterns.
- Efficient Resource Allocation: By understanding past trends, teams can allocate resources more effectively.
- Enhanced Predictability: Quantitative data helps predict future challenges and prepare accordingly.
Developing a Long-Term Testing Strategy
A long-term testing strategy is crucial for sustainable QA processes. It involves setting up guidelines, standards, and methodologies that will be used over an extended period.
Key Elements:
- Risk Assessment: Identify potential risks and develop strategies to mitigate them.
- Test Planning: Align test plans with business goals and user expectations.
- Continuous Learning: Regularly update strategies based on new learnings and industry trends.
Implementing Automation in QA
Automation is a game-changer in the world of QA. However, its success hinges on strategic implementation.
Steps for Effective Automation:
- Identify Automation Areas: Focus on repetitive, high-volume tasks, and areas prone to human error.
- Select the Right Tools: Choose tools that integrate well with your existing tech stack.
- Continuous Monitoring: Regularly review and update automated tests to ensure they remain effective.
Aligning with Company Deployment Strategy
Any QA strategy must align with the overall deployment strategy of the company.
Integration Tips:
- Understand Business Goals: Ensure your QA strategy supports the broader business objectives.
- Collaborate with Development Teams: Foster a culture of collaboration to ensure seamless integration of QA in the deployment process.
- Adaptability: Be prepared to modify QA processes as company strategies evolve.
Conclusion
Making evidence-based decisions in QA is not just about adopting new tools or technologies; it's about a mindset shift. It requires a balance between understanding data and aligning with the long-term vision of the company. As QA professionals, our goal should be to build robust, scalable, and efficient testing strategies that not only meet current needs but also adapt to future challenges.
Remember, in the dynamic world of software development, a data-driven, strategically aligned QA process is key to success.
80/20 Pareto Principle in QA
In the ever-evolving field of software testing, the Pareto Principle, commonly known as the 80/20 rule, has emerged as a cornerstone for efficient testing strategies. With a decade of experience in Quality Assurance (QA), I've seen firsthand how this principle can be a game changer in acceptance testing. In this blog, we'll delve into the Pareto Principle and its application in prioritizing test cases for acceptance testing.
Understanding the Pareto Principle
The Pareto Principle, initially observed by Vilfredo Pareto, states that roughly 80% of effects come from 20% of causes. In the context of QA, this translates to the idea that a majority of software issues are often due to a small portion of all possible causes.
Application in Acceptance Testing
Acceptance testing is a critical phase in software development where we verify whether the system meets the business requirements. It's the final checkpoint before the software reaches the end user, making the selection of test cases crucial. Here's how the Pareto Principle aids in this process:
1. Identifying Critical Test Cases
Not all test cases are created equal. Some have a higher impact on the overall system functionality than others. By applying the 80/20 rule, we focus on identifying the 20% of test cases that are likely to uncover 80% of the most crucial bugs. These often include core functionalities and features most frequently used by end-users.
2. Resource Optimization
In any project, resources ? be it time, manpower, or tools ? are always limited. The Pareto Principle helps in allocating these resources effectively. By targeting the most significant test cases first, teams ensure that the majority of potential defects are caught early, saving time and effort in the long run.
3. Risk Management
Acceptance testing is not just about finding bugs but also about risk management. The 80/20 rule aids in identifying areas with the highest risk and potential impact on the system's performance and stability. Focusing on these areas ensures that critical issues are addressed before the product release.
4. Enhancing Test Coverage
While it may seem counterintuitive, concentrating on the most impactful 20% of test cases can lead to better test coverage. This approach ensures that testing is more focused and comprehensive in areas that matter the most.
5. Continuous Improvement
The Pareto Principle also plays a vital role in the continuous improvement of the testing process. By regularly analyzing which test cases fall into the critical 20%, QA teams can adjust and evolve their testing strategies to stay aligned with changing user requirements and system functionalities.
Conclusion
Incorporating the Pareto Principle in acceptance testing is not just a strategy but a mindset shift. It encourages QA professionals to think critically about the value and impact of each test case. By focusing on the most significant test cases, teams can ensure that they are efficiently utilizing their resources while maintaining high standards of quality and reliability in the software they deliver.
Remember, the goal of applying the Pareto Principle in acceptance testing is to maximize efficiency without compromising on quality. It's about working smarter, not harder, to achieve the best possible outcomes in the realm of software quality assurance.
Wearing the Red Coat in Software Engineering
Introduction
In the world of software engineering, the Quality Assurance (QA) team often plays a critical, albeit understated, role. Drawing an analogy from Ozan Varol's insightful book, "Think Like a Rocket Scientist," we can liken the role of QA professionals to wearing the "Red Coat," a concept rooted in red teaming strategies. Here, I share insights from my decade-long experience in QA and explore how this role acts as the red team in the engineering world, ensuring the robustness and reliability of software products.
The Red Coat Analogy in QA
In "Think Like a Rocket Scientist," Varol describes how red teams play the adversary, aiming to uncover weaknesses in the blue team's strategies. In software engineering, QA professionals wear the Red Coat, symbolizing their role as the first line of defense against potential failures. We deep dive into the depths of software, much like a red team, to identify vulnerabilities, bugs, and areas of improvement that could otherwise lead to significant issues post-deployment.
QA: The Unsung Heroes in Engineering
QA teams often operate in the background, meticulously testing and retesting software to ensure its quality. Our work is crucial yet frequently goes unnoticed ? until something goes wrong. By rigorously challenging the assumptions and work of the development team (akin to the blue team), we prevent potential crises, safeguard user experience, and uphold the software's integrity.
The Proactive Approach of QA
The essence of wearing the Red Coat in QA is not just about finding faults but adopting a proactive approach. We don't just look for what is broken; we anticipate where and how software might fail. This forward-thinking mindset enables us to contribute significantly to the planning and development phases, ensuring that potential issues are addressed before they become real problems.
Collaboration and Challenge
Effective QA is not about working in opposition to the development team but in collaboration with them. We challenge assumptions not to criticize but to strengthen the final product. This collaborative tension is essential for innovation and quality, much like the dynamic between the red and blue teams described by Varol.
Tools and Techniques in QA Red Teaming
In our arsenal are various tools and techniques ? from automated testing frameworks to manual exploratory testing. We simulate adverse conditions, stress test systems, and think like the end-user, constantly asking, "What could possible go wrong?" Our goal is to ensure that when the software faces real-world challenges, it performs seamlessly.
Conclusion: Embracing the Red Coat Philosophy
As QA professionals, embracing the Red Coat philosophy means standing out and being the critical voice that ensures software excellence. Our role is vital in catching the unseen, questioning the status quo, and pushing for higher standards. In the grand scheme of software engineering, we are not just testers; we are guardians of quality, playing a pivotal role in the successful launch and operation of software products.
In conclusion, the next time you use a software application that works flawlessly, remember the Red Coats behind the scenes ? the QA teams who have tirelessly worked to make your digital experience seamless and efficient.
Bringing Fun to the Forefront of Quality
The Intersection of Enjoyment and Excellence
As a Quality Assurance (QA) professional with a decade of experience in software testing, I've learned that the most effective and enjoyable way to achieve excellence is by incorporating fun into the process. Here, I want to share insights on how infusing fun into QA practices can transform the way we approach software testing.
Why Fun Matters in QA
1. Enhanced Engagement: Fun in the workplace isn't just about enjoyment; it's a tool for better engagement. When QA teams are enjoying their work, they're more likely to be deeply engaged, leading to more thorough and creative testing.
2. Creativity Unleashed: Approaching tasks with a playful mindset encourages out-of-the-box thinking. This creativity is crucial in QA, where unconventional methods often uncover the most elusive bugs.
3. Stress Reduction: Software testing can be a high-pressure job. Integrating fun into our daily routines helps in alleviating stress, leading to improved focus and productivity.
Strategies for Incorporating Fun in QA
1. Gamification: Transforming routine testing tasks into games can be incredibly motivating. Leaderboards, challenges, and rewards for uncovering bugs can turn mundane tasks into exciting quests.
2. Team-building Activities: Regular team-building exercises, whether they're casual gaming sessions or problem-solving challenges, foster a sense of camaraderie and make the workplace more enjoyable.
3. Continuous Learning Culture: Encouraging a culture of continuous learning and experimentation keeps the work environment dynamic and intellectually stimulating. Hosting hackathons, innovation days, or learning sessions can be both fun and enriching.
4. Celebrating Successes and Failures: Recognizing both successes and failures in a lighthearted manner promotes a positive and balanced work culture. Celebrating 'Bug of the Month' or 'Most Innovative Test Approach' can add an element of fun to the team's achievements and learning experiences.
My Personal Approach: Fun with a Purpose
In my own journey as a QA professional, I've always strived to blend fun with functionality. Here are some personal practices I've adopted:
- Bug Bingo: Creating a 'Bug Bingo' card with different types of bugs. It's a playful way to encourage comprehensive testing.
- Mystery Missions: Assigning surprise 'mystery missions' where team members are given unexpected and fun tasks related to testing.
- Creative Brainstorming Sessions: Holding regular brainstorming sessions where no idea is too outrageous, often leading to innovative testing strategies.
Conclusion: Fun as a Serious Business Tool
In conclusion, bringing fun to the forefront of quality isn't about not taking our work seriously. It's about recognizing that enjoyment and engagement are powerful tools for achieving excellence in QA. By making our work environment more enjoyable, we're not just having fun; we're building a more effective, creative, and committed QA team.
Finding the Invisible Bug
Quality assurance (QA) plays an important role in ensuring that software products meet the required standards of functionality, usability, and reliability. One of the most challenging tasks for QA is to find the invisible bug - a bug that is not easily noticeable and may cause serious issues in the product.
The invisible bug can be elusive and hard to detect. It may occur only in certain scenarios, under specific conditions, or with certain combinations of input data. It may also have a subtle impact on the product's behavior, such as slowing down the system, causing data corruption, or making the product unreliable.
The key to finding the invisible bug is to approach the testing process with a critical and investigative mindset. QA should not rely solely on automated testing tools but also use exploratory testing, where testers manually interact with the product to identify potential issues.
Catching the Invisible Bug
QA should also test the product under different scenarios and conditions, including edge cases and negative testing, to uncover any hidden bugs. Edge cases are scenarios that lie at the boundaries of the product's functionality, where unexpected behavior may occur. Negative testing is testing the product with invalid or unexpected input data to see how it handles errors and exceptions.
In addition, QA should use various testing techniques, such as regression testing, integration testing, and performance testing, to identify any hidden bugs that may have been introduced during development.
Another useful technique is to involve stakeholders in the testing process, including product owners, developers, and end-users. Their input and feedback can help identify issues that QA may not have noticed.
Finally, it's essential to keep track of previous bugs and issues that have been fixed, as well as the product's history and development timeline. This knowledge can help QA identify potential areas of concern and focus their testing efforts accordingly.
Final Thoughts
In conclusion, finding the invisible bug is a challenging task for QA, but it is crucial to ensure that the product meets the required standards of functionality, usability, and reliability. By approaching the testing process with a critical and investigative mindset, using various testing techniques, involving stakeholders, and keeping track of previous bugs, QA can increase the likelihood of uncovering any hidden bugs and ensuring a high-quality product.
About
Welcome to QA!
The purpose of these blog posts is to provide comprehensive insights into Software Quality Assurance testing, addressing everything you ever wanted to know but were afraid to ask.
These posts will cover topics such as the fundamentals of Software Quality Assurance testing, creating test plans, designing test cases, and developing automated tests. Additionally, they will explore best practices for testing and offer tips and tricks to make the process more efficient and effective
Check out all the Blog Posts.
Schedule
Saturday | Internet Tools |
Sunday | Open Topic |
Monday | Media Monday |
Tuesday | QA |
Wednesday | iPhone 14 Pro Max |
Thursday | New England |
Friday | Macintosh |
Other Posts
- QA Memetober #4
- Engineer Sayings
- Best Screen Capture Tool for Chrome
- QA Memes
- What’s the best career advice you’ve ever had?
- Dragnet and QA
- QA Fail: Boston.com Headline graphic
- Picture in Picture in Chrome
- Dance is Like QA...
- The Seven Rules of QA
- Sprint Velocity
- Externalities
- Chrome Profiles vs Icognito Mode
- Test Pilot in Firefox
- Blue Green Deployment