Your SlideShare is downloading. ×
0
Automated
Automated
Automated
Automated
Automated
Automated
Automated
Automated
Automated
Automated
Automated
Automated
Automated
Automated
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Automated

311

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
311
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Structure: What it is/each part made of?Functions: What it does?Data: how it does it?Platform: what it depends upon?Operations: how it is used?Time: howit is affected by time?
  • Unit tests and functional system test are the obvious choice for automation. 70 % unit tests& 30% functional system tests will be optimal.
  • Transcript

    • 1. Automated test strategy
      Ingve Brunvoll
    • 2. What to automate?
    • 3. Test quadrants -Test coverage
      Supporting the team System tests
      Critique product
      Business tests
      Unit tests
      Technological
    • 4. Test quadrants – test strategy
    • 5. Test design
      Ingve Brunvoll
    • 6. Method
      1. Create a test plan for the area
      2. Analyze existing test coverage and tests
      2. Gather required coverage and missing tests
      4. Determine test cases to develop
      5. Determine what test oracles to use
      6. Automate? = Yes: Develop tests using keywords. No: Improve manual test forms.
    • 7. A functional test case
      Is an instance of a low level Use Case
      Is one of the pathways through a test scenario
      Can combine several positive, or at least one negative outcome
      Can operate on four test levels:
      Unit: Calling/Checking an atomic function
      Integration: Calling/Checking internal functions that again calls other functions
      System: Calling/Checking several functions when doing a specified user task
      Acceptance: How the functions/tasks and appearance are supporting the actual customers processes/needs
    • 8. Use case vs test case
    • 9. How to find Test oracles
      History versions
      Company image
      Comparable products
      Claims/documentation
      User expectations
      Product itself
      Purpose
      Statutes
    • 10. Test cases – base them on structured analysis
      Decision tables
      State charts
      User scenarios
      Boundary value analysis
      Careful and Un-ambigous Input/output value selection
    • 11. Best practise - automated test design
      Think broad, start small
      Use keywords for maintainability
      Risk based – start with the subset of tests that usually breaks and hurts most
    • 12. Automated test framework
      Ingve Brunvoll
    • 13. Test execution in framework
      Test case 1
      Test case 2
      Goal: Make each test independent of each other, and ensure they are not breaking each other, for max integrity & test confidence, reproducable in the simplest way, and ensure a detailed product status quality feedback to the team
    • 14. Keyword driven testing
      One test case consist of one or more keywords
      Keywords are used by the test driver to run specific test scripts
      Can represent technical concepts, functions, or be more abstract. i.e. represent a business model. Abstract keywords are more maintainable
      Keyword instances does not embed scripts itself
      Keywords and scripts can be reused by several test scenarios and test cases
      Are defined in XML templates and used by test cases in a decoupled fasion
      Keyword inherrits data driven testing, by sending parameters when invoking a keyword script library

    ×