• Promoting Agile Quality in a Corporate World

    Promoting approaches that truly increase quality can be a struggle in the Corporate worlds many of us live in. In this session Michael will relate recent tales of working in a large corporation that is still struggling to become Agile. He will share how he learned, even within large and slow traditional organizations, to successfully promote quality agile practices and approaches at all levels from senior management to SDETs on the ground. He will also share approaches that failed as they provide key learnings. Topics will include Scrum vs. Kanban, SAFe, KPIs, Six Sigma, Testing Pyramid, Test Ice Cream Cone and Test Iceberg, BDD, TDD, Visibility and Feedback. The session will include interactive surveys and open discussion with attendees who are encouraged to also share their experiences.

    5
  • Webinar: Lisa Crispin, Whole Team Testing @ Ministry of Testing, Ask Me Anything

    Lisa Crispin, co-author of "Agile Testing: A Practical Guide for Testers and Agile Teams" and "More Agile Testing: Learning Journeys for the Whole Team" ( http://AgileTester.ca ), and event organizer for the Ministry of Testing - Boston Meetup, will be giving an Ask Me Anything for the http://MinstryOfTesting.com . Register Here: https://www.ministryoftesting.com/events/testing-ask-me-anything-whole-team-testing-lisa-crispin About the "Ask Me Anything": "In this AMA, Lisa will answer questions about how whole-team testing works in practice. If you’re wondering how in the world you get non-testers interested in doing work that they’ve purposely avoided in the past, or interested in newer practices that involve more of the delivery team, such as pair and mob testing, please join in with your questions. "Once you've registered you could ask Lisa any question you might have, here are a few more examples: * "When I try to get developers to do testing, they say it’s not their job. What can I do about that? * "Other people on my cross-functional team say they want to learn how to do testing. How can I help them learn skills? What skills should I start with? * "I’m on a separate test automation team. It’s difficult to automate tests for (name some reason, such as, there are no unique identifiers in the UI). How can I get developers to make the code more testable?" Sponsored By: MABL Mabl, an excellent sponsor of the Ministry of Testing - Boston Meetup is also sponsoring this Ministry of Testing Ask Me Anything! "Mabl is the most reliable codeless UI testing service available, enabling continuous testing with an auto-healing automation framework and maintenance-free test infrastructure. Using proprietary machine learning models to automatically identify application issues, including JavaScript errors, visual regressions, broken links, increased latency, and more. Mabl brings traditional UI testing to the modern age. Find out more about http://mabl.com ". Want to Sponsor a Ministry of Testing worldwide event? * Advertise with the MOT: https://www.ministryoftesting.com/advertise * TestBash: https://www.ministryoftesting.com/testbash/sponsor Follow on Twitter: * Lisa Crispin: https://twitter.com/lisacrispin * Ministry of Testing: https://twitter.com/ministryoftest * Ministry of Testing - Boston: http://twitter.com/mot_boston * Mabl: http://twitter.com/mablhq * T.J. Maher: http://twitter.com/tjmaher1

  • *Note new Date/Time!* Test Auto Strategy Pt III: Put Your Strategy Into Practice

    We've postponed this to April 2 since I'm having knee surgery this week. See you then! I'm really excited about this installment. Bring your questions! This is a webinar event! In the first two installments of this webinar series, we looked at models based on the test automation pyramid, models based on the agile testing quadrants, and other shapes of visual models (even an iceberg!) to help identify risks and goals and help your team formulate a test automation strategy. In Part 3, you’ll learn guidelines for implementing your strategy, using a simple approach of running small experiments, then learning and adapting. See more details including learning outcomes, and register here: https://www.mabl.com/blog/webinar-modeling-test-automation-strategy-part-3 . Hope to see you there!

    1
  • Software Testing Lean Coffee @ John Harvard's, Harvard Square, Cambridge, MA

    What is a "Lean Coffee"? Picture a dinner-and-discussion group run like an Agile End-of-Sprint Retrospective. • Each Participant writes down on Post-It Notes topics they want to discuss. • After grouping up similar topics, each person votes on which topics they want to discuss. Each participant gets two votes to spend. • "Timebox" how long you want to spend on a topic. Five minutes? Ten minutes? • Time's up? Revote to add more time or jump to the next topic. How to RSVP: The Ministry of Testing - Boston Meetup has reserved an actual round table for this round-table discussion. Unfortunately, the table at John Harvard's pub in Harvard Square only fits fifteen people. If you RSVP "Yes", and you find out that you can't make it, please change your reservation. A wait list will be provided. Where to Meet: T.J. Maher will be next door to John Harvard's in The Garage from 6:00 pm to 6:20 pm if people wanted to gather early. We can head next door at 6:20 pm to see if the table is ready. T.J. is five-foot seven with short brown hair, blue eyes, a "Hello My Name is T.J." nametag, and will be sitting in the food court on the lower level. There will be a red MEETUP table tent next to him, and a red MEETUP sign attached to his black messenger bag. With such a large group, please try to bring cash to settle up the bill. About John Harvard's: John Harvard's is a brew pub, brewing their own beer, such as Brattle Blonde, Dunster Pale Ale, Imperial Stout, Be Hoppy, etc. You can see other beers they have listed on their website. Website: https://www.johnharvards.com/locations/cambridge-ma/ Dinner Menu: https://www.johnharvards.com/wp-content/uploads/Cambridge-Dinner-Menu.pdf With such a large group, please try to bring cash to settle up the bill. About the Event: T.J. will bring Post-It Notes and Sharpies for people to use. • We can pick discussion topics -- loosely related to software testing or quality assurance -- while looking at menus. • After reviewing the topics, grouping up similar ones in a "To Be Discussed" pile, we can vote on which we want to discuss. Each person can vote twice! Either twice on the same topic, or once on two separate topics. • How long does the group want to talk about the topic? Five minutes? Ten? We can go around the table to casually compare and contrast different viewpoints about the topic. The Post-It Note is in the "Discussing" pile. • Time's up? Do want to still talk about the topic? Extend it another five or ten minutes. If not, retire the topic in the "Topic Discussed" pile, and on to the next topic! About Lean Coffees: "Lean Coffee started in Seattle in 2009. Jim Benson (http://twitter.com/ourfounder) and Jeremy Lightsmith (http://twitter.com/lightsmith) wanted to start a group that would discuss Lean techniques in knowledge work – but didn’t want to start a whole new cumbersome organization with steering committees, speakers, and such. They wanted a group that did not rely on anything other than people showing up and wanting to learn or create". - LeanCoffee.Org (http://leancoffee.org/) "The Lean Coffee format is both easy to follow and effective at facilitating learning and collaboration through group discussions. Although the name combines ‘Lean’ (eg. Lean Thinking, Lean Startup, etc.) and ‘Coffee’ (implying casual morning sessions), neither the topics nor the meeting times need be so rigid. For instance, I’ve attended Lean Coffee meetups held in mornings, afternoons and evenings. You can gather at a local coffee house, a pub or at your office. Most successful Lean Coffee groups maintain a reliable cadence, meeting at the same time and place each week or two". - AgileCoffee.com (http://agilecoffee.com/leancoffee/)

    5
  • Your Code Hit Production, Now What?

    SmartBear

    It’s time to stop thinking of quality as something that can only be achieved before your code is released. Join SmartBear, Ministry of Testing, and Charity Majors as we discuss the need for testing in production and the importance of observability. Agenda: 6:00 - 6:30 --- Networking, Pizza & Drinks 6:30 - 7:15 --- Testing in Production: Yes You Can (And You Should), Charity Majors, Honeycomb.io 7:15 - 8:00 --- Westworld, Delos & The Perils of Ignoring Quality & Observability, Saoirse Hinksmon, SmartBear For those who can’t make it in person, this event will be live streamed starting at 6:30 PM ET at https://www.youtube.com/smartbear . Please do not RSVP to this event if you will not be attending in person. Testing in Production: Yes You Can (And You Should) Charity Majors Charity's Twitter: https://twitter.com/mipsytipsy Charity's Blog: https://www.honeycomb.io/blog/ Free eBook on Observability: https://www.honeycomb.io/resources/guide-achieving-observability/ Testing in production — it's gotten a bad rap. But here's the truth: you do it, I do it, everybody does it, and that's not a bad thing. You don't actually have a choice, since every deploy to production is an irreducibly unique combination of that artifact + deploy process + environment + point-in-time infrastructure. In other words, a test. So you already test in prod, like it or not ... but you probably haven't invested in enough tooling, so you probably do a shit job of it. Let's talk about how to test in production like a grownup — with guard rails and proper best practices, like canarying, feature flags, instrumentation and observability, human best practices and workflows, etc. Stop flushing senseless hours down the black hole for engineering time that is staging. Take back some of those precious hours and invest them in your production tooling instead. Why? Because production is the only environment that matters (besides your laptop). Most interesting problems are only going to manifest under real workloads, on real data, with real users doing unpredictable things under real concurrency and resource constraints. Replica environments are not valuable for helping us build up our instincts — secondary environments actually train us to expect faulty assumptions and take dangerous shortcuts. You should force people to develop and test in prod as much as possible; engineers should interact with production every day. This isn't even scary — and works for regulated environments too. Promise. Westworld, Delos, & The Perils of Ignoring Quality & Observability Saoirse Hinksmon Even though our lives are a bit more challenging than those of the characters in the popular TV series “Westworld,” the show still offers a few great lessons in the importance of quality and observability in your software development lifecycle, including the consequences of ignoring these two factors. Teams all over the world are feeling the pressure to move faster, increase performance, and continuously innovate, all without sacrificing the standard of quality that we as consumers have grown to demand. With the rise of Agile and DevOps, software development teams are learning to adapt to speed, take on new responsibilities, and continuously iterate on the processes they have in place. In this talk, we’ll dissect the successes and failures of the Delos team and how modern teams can learn from their mistakes to cultivate a culture of quality and observability within their own teams. We’ll cover team how transforming culture, workflows, and tooling that supports your need for visibility and continuous feedback can ultimately help you release quality code confidently and, of course, continuously.

  • Lightning Talks!

    Slalom Build

    Please join us for an evening of short talks, about 10 minutes each, on a variety of software testing related topics, on February 26. Slalom Build is hosting us, they're at 399 Boylston St in Boston. Their building requires visitor list entries, so please RSVP if you're coming as that will make getting in *much* easier. Doors will open at 6, with the program start at 6:30. Our hosts (web site https://www.slalombuild.com/): Slalom Build is a highly-scalable, high-velocity modern technology builder. We work with clients to close the distance between dream and reality, imagined possibility and technical realization. Simply put, we build the software that businesses run on, the products and experiences customers rely on, and the analytics that tie them both together. For tomorrow and well into the future. We are 100 builders and growing in Boston, come check us out! Partial Program: Testing in JavaScript with WebdriverIO is easier than you think Learn about why should you test in JavaScript if Java is so popular, how you can get started automating your desktop or mobile web applications using WebdriverIO to build large functional test suites, how to use page object model, build test suites and organize the tests. WebdriverIO is a JavaScript framework for E2E automation with simple and easy to read code. Andrey Chigarev is a Quality Engineer at Slalom Build who is focused on testing modern web applications on Angular, ReactJS, NextJS. WebdriverIO framework has been chosen as a testing solution for his 2 most recent projects. SeleniumBase: A reliable automation framework in Python for UI testing Standalone WebDriver scripts are prone to messiness and flakiness. SeleniumBase was built to deal with these issues and provide a more efficient solution for automated testing & continuous integration by wrapping WebDriver functionality into a complete test framework with Pytest. Michael Mintz DevOps and GroupThink: An Oxymoron? DevOps teams bring together specialists from disciplines with different views on what is most important which forms the basis for preventing groupthink. However, all closely-knit teams are susceptible to groupthink, a cultural attitude that implicitly rewards members whose striving for unanimity override their motivation to realistically appraise alternative courses of action. DevOps team members from different functional specialties may often defer to the expert in a particular realm to solve individual problems. This presentation examines the development of groupthink within DevOps teams. Gerie Owen is a QA Evangelist and Test Manager. She is a Certified Scrum Master, Conference Presenter and Author on technology and testing topics. She enjoys mentoring new QA Leads and brings a cohesive team approach to testing.

    3
  • Modeling your test automation strategy, part 2: Quadrants and other models

    Online webinar, *please register here:* https://zoom.us/webinar/register/WN_HFzFcXBuSJStJPJT5kZinw rather than here in meetup. If you can't attend the live broadcast, we will send you a link to the recording. In Part I of this series, we looked at the test automation pyramid and other triangle-shaped models that help teams visualize their test automation strategy. In Part II, we’ll look at other models you can use to talk about how to tackle the many challenges of test automation. The Agile Testing Quadrants model is useful for thinking about different types of tests, whether they should be automated, and who should participate in automating them. We’ll explore variations on the basic Quadrants model that might help in different contexts such as continuous delivery. There are several alternative quadrant and band pass models that you may find useful in deciding your test automation approach. We’ll also introduce visual techniques to identify risks and dependencies to consider as you form your automation strategy. Finally we’ll revisit another adaptation of the test automation pyramid that can identify gaps in your chosen strategy and help you adapt as you learn. Join the discussion live on February 6th, 2019 at 12PM EST.

  • Webinar: Tester Roles, Responsibilities, Value in Agile/Devops

    Online webinar with Lisa and Joel https://www.mabl.com/blog/changing-roles-of-testers-in-agile-and-devops **Please register via the link on the mabl website, rather than here!** As testers and QA professionals, the ways we contribute to the success of our software delivery teams continually evolves. At the same time we see new approaches to testing and building quality into software products. In 2018, we’ve heard many discussions about how testers and testing fit into DevOps and Continuous Delivery. We’ve seen new ways to learn how people use our software products in production. Modern Testing principles are triggering debates. Joel Montvelisky from PractiTest and Lisa Crispin of mabl meet up to talk about the challenges of leading changes in quality while organizations are focused on delivery speed and frequency. We welcome testers, test managers, developers, coaches and other team members passionate about quality to join us and bring your questions about how agile and DevOps teams build a quality culture. Bring your questions! If you can't attend live, it will be recorded, but please register to get notified when it's available. Talking points: * What are the main changes we see in the role, the responsibilities, and the value provided by testers that switch to work on Agile and DevOps teams? * Is adopting modern testing principles the path testers are taking today? * What is the future of testing? * Where do the test managers fit in? How can they help teams improve quality? * What is the most important message behind the DevTestOps manifesto to take home? (https://devtestopsmanifesto.org serves as a guide for testers working in a DevOps culture) * What needs to happen for more companies to take a more modern or contemporary approach to testing?

    1
  • Webinar: Jason Huggins: Ask Me Anything About Robots In Automation

    The Ministry of Testing would like to invite you to their next Ask Me Anything webinar, the only event where you can literally ask the speaker anything. Want to ask about a research paper or book the speaker has written? About something you gleaned from the speaker's Twitter feed? About the speaker's latest pet project? With a whole hour given for these sessions, almost all questions get answered! Register here: https://ministryoftesting.com/events/testing-ask-me-anything-robots-in-automation-jason-huggins January's AMA Speaker is Jason Huggins (https://twitter.com/hugs), creator of the first version of Selenium while he was at ThoughtWorks, Co-Founder and former CTO of Sauce Labs, and founder of Tapster Robotics (https://www.tapster.io/) which uses robots created to test iPhone and Android apps. Sample questions you can ask: * Why would a tester need a robot? * What can robots do that Appium or Selenium can’t do? * What are some scenarios where a robot is the right tool for the job? Jason talked on Joe Colantonio's Test Talks podcast about Selenium's creation back in January 2018: * https://joecolantonio.com/testtalks/188-preparing-robotic-automation-revolution-jason-huggins/ Jason also talked about with Joe Colantonio why Jason Huggins created Selenium, detailing some of the problems he was trying to solve: * Video: https://youtu.be/ZXUzDlY6aUw * Transcript: https://www.joecolantonio.com/selenium-jason-huggins-testing-tale/ What is Tapster? * Techcrunch: Tapster's robots are built to poke touchscreens: https://techcrunch.com/2018/03/31/tapsters-robots-are-built-to-poke-touchscreens/ To see Tapster robots in action, check them out on YouTube: https://twitter.com/tapsterbot More on Jason Huggins: Jason Huggins on Startup Life in CA and CHI, and How He Scored Twitter Handle @hugs https://saucelabs.com/news/jason-huggins-on-startup-life-in-ca-and-chi-and-how-he-scored-twitter-handle-@hugs "Chicagoan Jason Huggins is many things. A founder. A coder. An ex-Googler. A robot builder. A fixer of Healthcare.gov. "[...] "Huggins is a Chicago entrepreneur who has had one foot in the Windy City and one foot in Silicon Valley for the past decade. In the early 2000s he worked at ThoughtWorks, a Chicago-based software development company. There, Huggins created Selenium, a software testing tool for web browsers and applications. Basically, Selenium makes sure your code works on your site across all web browsers. Selenium earned Huggins what he calls his 15 minutes of tech fame, particularly from the software testing community, and in 2006 Google came calling. "Huggins moved from Chicago to Mountain View where Selenium was used mostly in-house to test things like Gmail and Google Maps. But even with the new gig, Huggins and his wife still couldn't leave Chicago for the Silicon Valley tech scene full-time. " 'I always kept it as a short-term thing,' he said. 'I rented out my house (in Oak Park) and we rented a house in Mountain View. We always had this idea that we were going to come back to Chicago.' Then in 2008, Huggins met his co-founders for what would be Sauce Labs, a startup that basically took what Selenium was doing for Google but made it available for other startups looking for software testing. SauceLabs would be headquartered in San Francisco, but Huggins made it clear he would be working out of Chicago. " 'I told (my co-founders), "We can start this. I can totally be your implementor of these thing. But I’m moving back to Chicago."' "So for two years Huggins worked as Sauce Labs' CTO from Chicago and traveled once a month back to California to meet with his team. Huggins is a self-described ideas man rather than a manager of talent, so he was happy to leave those duties to his co-founders. [...]"

  • Webinar - Modeling Your Test Automation Strategy with Lisa Crispin

    This is the first of a 3 part series I'm doing on using visual models to help you create a viable test automation strategy. It will be recorded, so if you can't attend in person, please register anyway so you can get the link to the recording. These will be short webinars with lots of time for questions. Learn more here and register: https://www.mabl.com/blog/webinar-modeling-your-test-automation-strategy-exploring-the-pyramids (though it is a mabl-sponsored webinar, it is not mabl related).

    2