KICK STARTING
TEST AUTOMATION
RUZAIK REFAI
KICK STARTING TEST AUTOMATION
ASSUMPTIONS
▸A system to automate.
▸A (manual testing) test plan.
KICK STARTING TEST AUTOMATION
STEPS
1. Convince the client
2. Create a test plan (in the absence of one) including
configurations
3. Find test automation experts
4. Find the appropriate tool(s)
5. Create the test automation framework and scripts
6. Implementing/integrating with CI/CD
The above steps
are merely a
guideline!
KICK STARTING TEST AUTOMATION
CONVINCE THE CLIENT - I
Different types of customers
๏ Non technical - No clue about automation
๏ Techie but fails to see the need to automate
๏ Those who don’t want to invest (time and/or money) in test
automation
KICK STARTING TEST AUTOMATION
CONVINCE THE CLIENT - II
Myths:
๏ Test automation will replace manual testing
๏ Anything & everything can be automated
๏ Automated testing > manual testing
๏ Quick/immediate ROI
๏ Customer will never see the results of automation
KICK STARTING TEST AUTOMATION
CONVINCE THE CLIENT - III
Facts:
✓ Initial investment is high (time, resources, etc)
✓ Can be run at any time convenient
✓ Reduces the workload for manual testing
✓ Diligent
✓ Simultaneous/parallel execution
✓ Consistent and accurate
✓ Improves test coverage
✓ Reusability
KICK STARTING TEST AUTOMATION
CREATE A TEST PLAN
▸Identify suitable test cases to automate.
▸Identify the environment + device configurations required.
▸Do NOT automate:
A test that runs only once.
An unstable feature; constant UI/functional change.
Usability tests.
Tests that require a human’s opinion
Why now? Why not earlier?
KICK STARTING TEST AUTOMATION
FIND A TEST AUTOMATION EXPERT
‣ To do the scripting
‣ Benefits:
✓ Reduce the learning curve
✓ Reduce the chance of neglecting manual testing
✓ Help decide on an appropriate tool
✓ And many more!!!
KICK STARTING TEST AUTOMATION
FIND THE APPROPRIATE TOOL(S)
KICK STARTING TEST AUTOMATION
TEST FRAMEWORK + SCRIPTING
Is it maintainable?
Is it reusable?
Is it parameterised?
KICK STARTING TEST AUTOMATION
IMPLEMENTING/INTEGRATING WITH CI/CD
TEST AUTOMATION DOES
NOT MEAN MORE TESTING
IN LESS TIME; IT MEANS
MORE TESTING IN THE
SAME TIME.
Software Testing Help
KICK STARTING TEST AUTOMATION

Kick Starting Test Automation

  • 1.
  • 2.
    KICK STARTING TESTAUTOMATION ASSUMPTIONS ▸A system to automate. ▸A (manual testing) test plan.
  • 3.
    KICK STARTING TESTAUTOMATION STEPS 1. Convince the client 2. Create a test plan (in the absence of one) including configurations 3. Find test automation experts 4. Find the appropriate tool(s) 5. Create the test automation framework and scripts 6. Implementing/integrating with CI/CD The above steps are merely a guideline!
  • 4.
    KICK STARTING TESTAUTOMATION CONVINCE THE CLIENT - I Different types of customers ๏ Non technical - No clue about automation ๏ Techie but fails to see the need to automate ๏ Those who don’t want to invest (time and/or money) in test automation
  • 5.
    KICK STARTING TESTAUTOMATION CONVINCE THE CLIENT - II Myths: ๏ Test automation will replace manual testing ๏ Anything & everything can be automated ๏ Automated testing > manual testing ๏ Quick/immediate ROI ๏ Customer will never see the results of automation
  • 6.
    KICK STARTING TESTAUTOMATION CONVINCE THE CLIENT - III Facts: ✓ Initial investment is high (time, resources, etc) ✓ Can be run at any time convenient ✓ Reduces the workload for manual testing ✓ Diligent ✓ Simultaneous/parallel execution ✓ Consistent and accurate ✓ Improves test coverage ✓ Reusability
  • 7.
    KICK STARTING TESTAUTOMATION CREATE A TEST PLAN ▸Identify suitable test cases to automate. ▸Identify the environment + device configurations required. ▸Do NOT automate: A test that runs only once. An unstable feature; constant UI/functional change. Usability tests. Tests that require a human’s opinion
  • 8.
    Why now? Whynot earlier? KICK STARTING TEST AUTOMATION FIND A TEST AUTOMATION EXPERT ‣ To do the scripting ‣ Benefits: ✓ Reduce the learning curve ✓ Reduce the chance of neglecting manual testing ✓ Help decide on an appropriate tool ✓ And many more!!!
  • 9.
    KICK STARTING TESTAUTOMATION FIND THE APPROPRIATE TOOL(S)
  • 10.
    KICK STARTING TESTAUTOMATION TEST FRAMEWORK + SCRIPTING Is it maintainable? Is it reusable? Is it parameterised?
  • 11.
    KICK STARTING TESTAUTOMATION IMPLEMENTING/INTEGRATING WITH CI/CD
  • 12.
    TEST AUTOMATION DOES NOTMEAN MORE TESTING IN LESS TIME; IT MEANS MORE TESTING IN THE SAME TIME. Software Testing Help KICK STARTING TEST AUTOMATION

Editor's Notes

  • #4 Emphasise that these steps are merely a guideline. Sometime they might have to be adapted as per the circumstances.
  • #5 The final category is refers to those who know about automation and know of its benefits but are too cheap to invest. The nay-sayers; they will always say, “NO”
  • #7 Sometimes convincing a client will have to take place after developing a POC.
  • #9 In the case of having to develop a PoC before convincing the client, this might be someone who could “consult” on the PoC; such as a member of the automation drive or an intern even.
  • #10 Look at the available tools See which ones support the product’s technology stack Paid vs Free: sometimes a paid tool is a necessity