LEARN ABOUT HOLISTIC TESTING STRATEGIES THROUGH

Holistic Testing: Strategies for agile teams - “Holistic testing - quality overall and on each step of release cycle. General things I got from this training: o) testing != tester ONLY responsibility, but whole team effort is required find language to communicate within the team to bring changes. Some might have tunnel vison, so remember to zoom out sometimes. o) involve QA in all steps of development o) built in quality withing the team for better delivery o) Team Expectations workshop - what do you except from each of your team members o) Think outside the box - holistic testing... Can the developers expand their unit test framework to do some of the functional stuff if test was worth writing & automating -> don't ignore it if it fails (flaky tests); fix the code or fix the test; 100% of regression tests must pass, ALL the time; o) Refactor to keep them clean and up to date o) respect within the team o) enable collaboration - do not force it! o) involve developers into testing o) slice US - use Story mapping approach (include the whole team);  https://www.humanizingwork.com/the-humanizing-work-guide-to-splitting-user-stories/ https://www.amazon.com/Fifty-Quick-Ideas-Improve-Stories/dp/0993088104?ref=d6k_applink_bb_dls&dplnkId=1ddfe800-a031-4605-9836-c2659d836c0c o) Refinement: Unknown/unknown concept -> means don't understand what we don't understand; act like a child and ask stupid questions; SFDPOT approach (structure; function; data; platform; operations; timing/performance). When discussing functionality -> create real people (person), give them role and write how would their use your product (Dabby 75 year old granny who loves her grandchildren is going to a birthday party tomorrow, wants to buy a present for her grandchild but doesn't trust technology and usually gets help in the library -> concept) create a system diagram to better understand your dependencies/how it works; afterwards discuss within the team Test Coverage - how much is covered by autotests. Tools to be used: c4model.com; xmind; draw.io; o) automation is responsibility of the whole team o) if testers are struggling to finish their tasks, then devs should not take next big items, but rather help tester with testing what is possible and take small items or analyze US in a backlog”