STLDODN - Agile Testing in a Waterfall World

Far too often agile adoptions focus just on the development teams, agile frameworks, or technical practices as a part of their adoption strategies. And then there’s the near perpetual focus on tooling or developing test automation without striking a balanced approach. Often the testing activity and the testing teams are “left behind” in agile strategy development or worse yet, they’re simply “along for the ride”. That is not an effective transformation strategy. Join experienced agile coaches Bob Galen and Mary Thorn as they share the Three Pillars framework for establishing a balanced strategic plan for effective quality and testing. The Three Pillars focus on development and test automation, testing practices, and collaboration activities that will ensure you have a balanced approach to agile testing. Specifically, risk-based testing, exploratory testing, paired collaboration around agile requirements, agile test design, and TDD-BDD-Functional testing automation will be explored as tactic within a balanced Three Pillars framework. You will leave with the tools to immediately initiate or re-tool a much more effective and balanced agile testing strategy. ortion pills to be shipped to house

QASYMPHONY & BLUEPRINT PARTNER UP Learn about the new partnership between QASymphony and Blueprint. Connecting software requirements with proper test coverage still remains an age old problem for software development teams. This new partnership will provide alignment between requirements and testing teams of all types to get the visibility and traceability needed to understand their requirements coverage. In this webinar, Kevin Dunne, QASymphony's VP of Strategy and Business Development and Ruth Zive, VP of Marketing at Blueprint will answer the following questions: What is QASymphonys qTest Platform? How is this platform enhanced by Blueprint? How does the integration between qTest and Blueprint work? Why does your team need this offering?

This document discusses exploratory testing (E.T.) and how to effectively implement it. It begins by defining E.T. as simultaneous learning, test design, and execution. It then contrasts E.T. with scripted testing, noting that E.T.'s goal is to find bugs while scripted testing aims to measure coverage. The document provides tips for doing good E.T., such as keeping notes and using different testing styles. It also discusses managing E.T., including using sessions and balancing E.T. with other testing. Lessons learned emphasize the benefits of pair testing and that E.T. requires skilled testers and planning to be successful.

Mithun R has over 3 years of experience as a QA analyst and automation tester. He has worked on projects in the banking domain for clients like Citi Bank. Some of his responsibilities include designing and executing test plans, writing test cases, defect tracking, and ensuring compliance. He is proficient with tools like HP Quality Center, HP ALM, and QTP. He has experience in testing techniques like system integration testing, mobile application testing, and regression testing.

The document provides answers to frequently asked questions about manual software testing. It discusses introducing new QA processes, the role of documentation, qualities of a good test engineer, definitions of a test plan, test case, and other key testing terms. It also offers advice on issues like handling bugs, testing with changing requirements, and knowing when to stop testing. The overall focus is on best practices for planning, executing and improving manual testing processes.

How to identify and leverage useful metrics vs harmful metrics. Rules of good metrics; values to apply and principles to follow when measuring the well-being of a company's people, process, and product.

This document discusses agile testing methodology. It begins with general concepts of agile testing such as testing from the customer perspective as early as possible. It then discusses agile testing methodology, challenges, test levels from first to third view perspectives involving extreme testing, exploratory testing, and collaboration between development and testing. The document also covers benefits of being an agile tester such as working as one team towards a common goal. In conclusion, it states that agile testing is useful, less time consuming and effective from the customer's point of view when automated testing is performed and developers, testers and customers work together as a team.

Presenter: Anne Hungate President, Daring Systems You’ve heard about Continuous Integration and Continuous Delivery but what’s common as code makes its way through those processes? Testing. With DevOps Testing (also known as Continuous Testing), testing tasks are engineered to be continuously completed end-to-end across the entire development to deployment pipeline. Developers, QA analysts, security professionals, IT Operations analysts…everyone is a tester in a DevOps environment. Join us to learn more about DevOps Testing and the emerging role of DevOps Test Engineer.

The document provides guidance for managing a team of junior testers. It discusses challenges such as lack of skills and experience in junior testers. It recommends setting clear expectations, providing frequent communication and feedback, ensuring knowledge sharing, and protecting the team to help them succeed. Patience and structure are important, as is repeating key messages, to help junior testers learn and improve. The goal is for the team to work cooperatively toward a common objective.

Modern software testing for Healthcare Organizations. Learn about best practices for software testing in the healthcare industry featuring Mike Cooper, Chief Quality Officer of Healthcare IT Leaders and Kevin Dunne, VP of Business Development at QASymphony

European IT industry need to deal with a huge salary gap with developing countries. How can we increase our productivity and quality to compensate for the salary differences? This is a systems-thinking / Lean based approach to that problem

The document discusses 10 signs that an organization's software testing may not be enough. These include having excessive production bugs, bugs found during user acceptance testing, growing bug counts over test cycles, not investing in testing compared to competitors, lacking clear criteria for what constitutes "enough" testing, testers advising against releasing software, weak prevention efforts like code reviews, lack of developer unit testing, frequently reduced testing periods causing deadline problems, and high tester turnover. The document advocates treating testing as risk management, increasing test reuse and automation, and addresses common challenges and questions around software testing.

This document contains three short anecdotes from Randy Rice about his experiences with test automation projects. The first story describes a project where daily technical reviews of test automation code were required to ensure all consultants were following the defined approach. This helped address issues but some consultants resisted and did not last on the project. The second story explains that a company's original test automation was not maintained during two major projects, leading the automation to become outdated and necessitating a restart. The third story relates a project where automating a system's daily regression tests through a vendor's proof-of-concept led to quick success and benefits for a manual tester by freeing up their time.

Last week we hosted a webinar, “Streamlining Automation Scripts and Test Data Management”, to compliment the release of qTest 8.1. This webinar covers Test Data Management, QASymphony’s new Automated Script Generator, and new UI for the qTest eXplorer Session Manager

With a short introduction to the role of Product Owner in a Scrum team, this lecture aims at demonstrating the unique leadership role that the business representative could and should assume in agile projects. Business representative as a Product Owner provides more direct availability of functional knowledge and stakeholder expectations to the project. Decisions can be taken on the spot. Mutual understanding of the business and development perspective is much higher, so any functional, budgetary, legal or other issue is less demanding. But great power of Product Owner comes with huge responsibility – as this person’s professional life becomes dedicated to the well-being of the project and the product being developed. Lecturer will provide a hands-on experience with thinking and collaboration tools and practices in moving and shaping a product vision to a product that the end-users will love.

This document discusses why checklists are better than test cases for documentation in quality assurance. It argues that test cases become overcrowded and focus too much on documentation rather than core functions. Checklists are more time-saving and easy to update. An example compares a test case to a checklist for login/registration flows. The author's company Hipo uses a test pad and robot framework integrated with checklists to share with clients and team members.

The document discusses several agile concepts including the Agile Manifesto, Scrum, Extreme Programming (XP), Test-Driven Development (TDD), and coding dojos. It outlines the values and principles of the Agile Manifesto which emphasize individuals, interactions, working software, customer collaboration, and responding to change. It then provides brief descriptions of Scrum roles, ceremonies, and artifacts as well as XP practices like pair programming, writing unit tests first, and integrating often.

The document discusses agile testing principles and processes. It compares agile testing to waterfall testing and outlines some key differences. It also addresses topics like continuous integration, test automation, managing test cases and issues, and transitioning from waterfall to agile. Pseudo-agile projects are described as those that claim to use agile but lack key elements like automation, continuous integration, or involvement of testers throughout the process.

Webinar "Differences between Testing in Waterfall and Agile" presentation by Maria Teryokhina http://www.exigenservices.ru/webinars/testing-in-waterfall-and-agile

The document describes a software testing professional's experience transitioning from the waterfall development model to agile. It discusses the challenges of adapting to agile practices like limited documentation, continuously changing requirements, and estimating work. The professional initially struggled but eventually saw benefits like increased productivity, transparency, and ability to adapt to changing customer needs. Tools like Rally also helped replace ALM by providing a single source for requirements, defects, testing, and reporting. Overall, agile allowed for faster learning and delivery with high customer satisfaction.

1 hour version of my talk delivered to ACT - W: Overview of what Imposter synrdrome looks like and feels like, and some techniques for harnessing the good parts of Imposter Syndrome , in yourself and others