Software Quality Assurance

    Agile Test Strategy Big picture (ten words or less to speak to what this is that we are testing) Drive behavior and set testing boundaries Outline automation approach (typically executed after end-to-end testing) Test data management (need to have clean data or will any data do?) Test data should be re-usable and accessible in non-production environments Collaborate with your data Team and Engineering Team Defect management UAT bug definition as agreed on by Product QA bug Create a ‘Bug’ and link to the story that the bug has been found in Communicate to the Product owner for priority and assignment   When a bug is blocking a ticket, send an email to all stake holder stating so Bugs ought to be resolved in the same sprint or carried over into the next sprint with the relative ticket  If the bug is NOT resolved and the ticket needs to move to Production then we will put it in the backlog and label with #techdebt Large risks to our product quality Our mindset is on...

 Being dyslexic has meant that my approach to learning has taken an un-traditional approach 

  This is Strange  We'll learn more about each other organically This is intended to quickly mention a few things to better understand me  This is not a presentation, but an info deck (https://martinfowler.com/bliki/Infodeck.html) Part of having this be known by the team is so that you can all hold me accountable for my actions What I do Attract and Retain World-Class Talent (that's you!) Set context and provide clarity  When I do something that negatively impacts my ability to retain you, tell me, (or if you’re more comfortable my boss), ASAP.  If I do something that feels more like telling you how to do your job rather than setting context, tell me ASAP. How I approach my job Autonomy - you decides how you do your work we each own what we do Learn - continue to learn and do better for yourself and for the Enterprise be open about what you don’t know and be willing to learn Purpose - Align your work with a high power, customer, Team, OKR, … We are the Team that...

 What is a full stack QA ?  Manual tester and SDET?  Test the front, back, middle and side to side? 

 Docker, Kubernetes like peanut butter and jelly Selenium web driver  Maven  Jenkins  list more here later    

 https://youtu.be/Jm6FHfodSbg

 Tell me I'm wrong? Testing is only a cog in the quality machine. There are so many other aspects of what is comprised of quality, user experience being the first that comes to mind that may be exposed by testing but is still something that must be reflected on if we're talking quality. Telemetry is another; how are we measuring the thing that matter when it comes to quality? 

 IT QA is NOT the same as Software QA

In 2017 I was determined to leave IT finance; I had enough of Banking and Mortgage, so I took a nice long break spent time w/ the family and our new one year old. And found my dream job; I mean literally after interviewing I had literal dreams of working there; walking on the bluffs and solving complex software quality engineering problems, (don't judge my dreams).  Over the course of 2018 my commute was over an hour long even with a few speeding tickets, BUT it was worth it. I loaded up every leadership book I could listen too and bought in hook line and sinker to my new gig's philosophy went from 1990's on premise infrastructure  all .NET with Test Professional, Selenium web driver/C# and MS Office to AWS, ruby, Cyprus, jira, confluence and Google office. The rate of learning, lack of sleep and stress had my my skin break out in eczema that a still have today, i had put on weight, even though we had on-site yoga and gyms w/ my commute I would sacrifice the work out to see...

  Who's wants to engineer testing verses those that want to engineer quality?  Testing is NOT Quality, only ONE tool to reflect your product's quality.  QA = Quality Advocacy QE = Quality Engineering  SDET = Software Developer Engineering in Test