VISION CI - CD
• EVERYBODY SHOULD BE ABLE TO DEPLOY
• THERE WILL BE NO DIFFERENCES BETWEEN
DEPLOYING HOTFIX OR FEATURE. IT CAN BE
RELEASED ANYTIME ANYWHERE.
METRICS AND KPIs
• SET GOALS -> PEOPLE WILL BE
ENCOURAGED TO REACH
• BUT… THERE IS ANOTHER THING THAT ALSO
IMPORTANT!
• TRENDS OF INCREASED VALUE OF EACH
METRICS / KPIs
Slide 12
Slide 12 text
BUG PREVENTIONS VS
DETECTIONS
• What to expect from automated tests?
• Testers should be assisting developers to
prevent bugs, not only hunting bugs
• Developers should not believe QA will catch
bugs
Slide 13
Slide 13 text
ROLES OF QA in
ATLASSIAN
• QA == Quality Assistance != Quality Assurances
• Teach developers to tests
• Assessing risks
• Prevent problems
• Ensure quality is everybody’s responsibility
Slide 14
Slide 14 text
TEST AUTOMATIONS
• AVOID REPETITIVE TASKS
• FASTER AND MORE FREQUENT FEEDBACK
• SAFETY NET ( REDUCE RISKS OF RELEASING
BUGS )
• IT SHOULD NEVER FIND ANY BUGS. IT MEANS
OUR CODE HAS GOOD QUALITY.
Slide 15
Slide 15 text
TEST AUTOMATIONS (2)
• REINVEST TIME. TESTERS / DEVELOPERS TIME
CAN BE USED TO DO ANOTHER THINGS
• NOT TO REPLACE HUMANS
• BUY TOOLS IF NEEDED
Slide 16
Slide 16 text
TEST AUTOMATIONS (3)
Slide 17
Slide 17 text
TESTING FOR THE FUTURE
• TDD
TEST CONTINUOUSLY ALONGSIDE
DEVELOPMENT
• ALL TESTS ARE DONE WITHIN SPRINTS
• TESTING IS EVERYBODY’S RESPONSIBILITY
Slide 18
Slide 18 text
MINDSET TO BE ACHIEVED
• WE ARE NOT ONLY CREATING THINGS
• WE TEST EVERYTHING
• WE SHOULD BE ABLE TO DELIVER OUR CODE
TO CUSTOMER AUTOMAGICALLY
• TEST SHOULD BE PART OF OUR DNA
• BIG MINDSET CHANGES REQUIRED
Slide 19
Slide 19 text
CHANGES?
• DON’T BE AFRAID TO MAKE CHANGES
• DEVELOPERS SHOULD THINK AS TESTERS
• TESTERS HAVE MINIMUM KNOWLEDGE TO
DISCUSS THINGS WITH DEVELOPERS
Slide 20
Slide 20 text
CHANGES (2)
• CULTURE:
• FREEDOM
• OK TO FAIL
• INNOVATIONS
• OWNERSHIP (REDUCE IT’S NOT MY JOB IDIOMS)
• PRODUCT OWNERS SHOULD BE INVOLVED FROM
START TO FINISH
Slide 21
Slide 21 text
SOME NICE QUOTES (1)
• IF YOU’RE NEW STARTUP, FOCUS ON WHAT
MATTERS AND RELEASE FASTER.
• BUT DON’T FORGET TO FILL THE GAPS IN
TESTING BECAUSE IN THE FUTURE IT’S
GOING TO BE NEEDED.
• ESPECIALLY WHEN FEATURES ARE ADDED
AND ADDED
Slide 22
Slide 22 text
SOME NICE QUOTES (2)
• TDD GIVES US CONFIDENCE WHEN WE ADD
NEW PEOPLE
• IT WILL ENSURE HE CAN CHANGE ANYTHING
WITHOUT AFRAID TO BROKE ANYTHING OR
AT LEAST HE KNOWS WHAT’S BROKEN
Slide 23
Slide 23 text
SOME NICE QUOTES (3)
• TDD MIGHT SLOW US DOWN WHEN WE
IMPLEMENT IT IN THE MIDDLE
• BUT IT WILL HELP US AVOID HARDER
SITUATIONS WHEN FEATURES ADDED IN THE
FUTURE
Slide 24
Slide 24 text
SOME NICE QUOTES (4)
• IT’S IMPOSSIBLE TO MAKE HUMAN FOLLOW A
LOT OF WRITTEN TEST SCENARIOS
• IT SHOULD BE AUTOMATED, BUT NOT
EVERYTHING COULD BE AUTOMATED
• EXAMPLE: PEN TESTS / SECURITY TESTS
Slide 25
Slide 25 text
SOME NICE QUOTES (5)
• CODE REVIEWS HELP DEVELOPERS LEARN
ANOTHER PEOPLE CODES
• INTERESTING PART IS WE SHALL ALLOW
PEOPLE WHO’RE NOT WORKING WITH THE
PARTICULAR FEATURES TO GIVE FEEDBACKS
• IT’S HOW OPEN SOURCE WORKS
Slide 26
Slide 26 text
SOME NICE QUOTES (6)
• IF ONLY SPECIFIC PEOPLE OWNS
PARTICULAR CODES, IT MIGHT MAKES US
TRAPPED TO FOLLOW SPECIFIC STYLES AND
CANNOT FOLLOW OTHERS
• IT MIGHT MAKE A SINGLE POINT OF FAILURE