Let’s take a look how the process of quality assurance has evolved in Cognifide. I would like to take you on a journey through the transformation of quality assurance process in our company from the dinosaurs to the electrically driven car sent into space. The short history from script approach to exploratory testing, from Testers to Quality Assurance Engineers, from manual to automated approach, from Quality Assurance to Quality Assistance, from Continuous Integration to Continuous Delivery and many other elements of our software quality path. Have we found an ideal and bulletproof Quality Assurance process? Has the evolution finished? If not, what’s next? Adam Makarowicz – Principal Quality Assurance Engineer in Cognifide. 8 years of experience in software testing. A highly motivated person who always tries to find the most effective solution in any situation. Working closely with clients to overcome their difficulties and help them to reach their business goals. Swiftly changing hats of QA Lead, Technical Lead, Business Analyst to learn, share and accommodate project and company needs.

1. The Quality, or There and
Back Again
Adam Makarowicz
March 13, 2018
1

2. Adam Makarowicz
Principal Quality Assurance Engineer
8 years of experience in software testing
QA Lead, Technical Lead, Business Analyst, Product Owner
2
About me

3. Introduction
The Quality
There and Back Again
3

4. Starting point
4

5. First JIRA workflow
5

6. Try to improve it
6

7. Testing in progress and Tested
7

8. Better now?
8

9. Code Review
9

10. 10
Exploratory testing
Exploratory approach
 QA designs and executes tests simultaneously
 relies on empirical knowledge
of the tested application
 supports creativity
 emphasizes personal freedom
and responsibility
 continuously optimizes the quality
of tested work
Learn
Test
Design
Test
Execution
Analysis

11. 11
Standard checklist
A pre-scripted standard checklist:
 list of standard aspects of the application that
must be checked
 avoid situation when core features are not
tested
 each project defines its own standard
checklist based on its platform requirements

12. 12
Test cases

13. 13
Session based approach, charters
Plan, execute and report the results of the exploratory session using the session based
approach.
 charter – goal or agenda for the test session
 follow the mission of the session
 take notes during the session
 report your findings
 use tests session templates

14. 14
Cross testing
 No duplication
 Based on session notes
 Great to learn how to test

15. 15
Test sessions debrief
 Time effective
 More agile
 Speed up testing process

16. 16
Pair testing
 Integration
 Learning more effective

17. 17
Testers on definition

18. 18
A lot of rejects

19. Reactive -> proactive
19

20. 20
Developer checklist
 Demo content
 Tested locally
 Documentation

21. 21
Automation
21
End to end
tests
Author feature
tests
Visual comparison
HTML comparison
JS errors
Design responsiveness
3rd party integrations
API / micro services tests
Unit tests
Code quality validation

22. 22
Definition of Done
Definition of Done
 Task developed
– tests executed (acceptance and exploratory)
– regression tests done
– non-functional tests done
 Maintainability achieved
– automated tests implemented
– documentation done

23. Daily work
23

24. To do
24

25. 25
Definition of Ready
Definition of Ready
 Requirements defined
 Requirements understandable and testable
 Impact assessment done
 Set of tests selected
– functional and non-functional
– regression
– automated
 Implementation design done
 Estimated

26. 26
Three amigos and daily grooming

27. 27
BDD in stories

28. 28
BDD in automation

29. 29
Cognifide standards
Cognifide standards elements
 Browser support
– author and publish supported browsers
 End user experience
– responsiveness, JavaScript support, pixel perfect, images and
video quality, authoring flexibility, markup, accessibility
 Customisation
 Authoring experience
– dialog usability, components, consistency
 Performance
– application, infrastructure, caching
 Maintainability and extendibility
– logic, error handling, documentation, static code analysis, code
Review, integration approach, software versions
 Testing
– Level of tests, SEO, regression, test scripts, reporting,
automation, release and deployment procedure
 Security
– application, infrastructure
 Content maintenance and support
 Infrastructure maintenance
– monitoring, hosting maintenance, web server configuration

30. 30
QUBACZ
 Code coverage
 Abstract interpretation
 Cyclomatic complexity
 Compiler warnings
 Coding standards
 Code duplication
 Fan out
 Dead code

31. 31
QA Audits
 Audits vs Review
 Reporting
 Mentoring
 Monitoring

32. 32
Too many rejects – extended AC should be tested

33. QA vs Tester
33

34. No longer testers
34

35. 35
QA hug
 Define Developer responsibility
 Create test ideas
 AC updated

36. 36
QA Dev demo
 Prove that feature works
 Show all AC to QA
 Green/amber/red features

37. 37
QA Validation consist non-functional
Non-functional
initial checks
Specific
requirements
i.e.
Localisation
Performance
Accessibility Security

38. Continuous delivery
38

39. 39
Continuous delivery + Progressive UAT
Feature 1 Feature 2 … Feature N
UAT for Feature 1
UAT for Feature 2
…
…
Deployment of
Feature 1
Deployment of
Feature 2
F1
Sign-
off
F1
done
F2
Sign-
off
F2
done
…Sig
n-off
…don
e
Feature1Feature2Feature…

40. User story production
40

41. User story production
41

42. Recent changes
42

43. Delivery status extended
Footer can be updated or switched off by going to Insert > Header & Footer 43

44. 44
Versioning from JIRA -> Bamboo

45. Blue green concept
45

46. Out of the box thinking
46

47. 47
Bug hunting
How?
 all QA practice members in one room
 we test and explore any application
 we take a 2-hour timebox to find defects
and improvements
 we log all things in one place
 rules & scope are defined by the project
When?
 in the middle of a project timeline
 before the UAT phase

48. Balance
48

49. 49
Balance

50. 50
Thank You.
Adam Makarowicz
Skype: a.makarowicz
adam.makarowicz@cognifide.com