YOU ARE DOWNLOADING DOCUMENT

Please tick the box to continue:

Transcript
Page 1: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

Automated TestingSaving Time & MoneyBlayn ParkinsonE-Learning & training Support Assistant

University of York (UK)

Page 2: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

ABOUT ME

Blayn ParkinsonE-Learning & Training Support AssistantUniversity of York (UK)[email protected]

I have used Blackboard for 3 years.

Page 3: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

ABOUT MY INSTITUTION

University of York

15,330 Students

Using Blackboard since 2005.

Central e-Learning team 6 members (some departments have their own provision)

Page 4: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

WHAT WE ARE GOING TO LEARN TODAY

• The benefits of using automated testing strategies.

• Limits to automated testing

• Suggestions on future collaboration in this area

Page 5: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

OUR CHALLENGE

Thorough testing cycle ( each software not deployed without testing).

3 months: April – June (One window a year to achieve this).

• Lack of agility in responding to new releases, due to the testing time that we need to devote to a release.

• Needed to lock in to a release at a particular time.• Spread the load across the team in terms of manual testing.

Page 6: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

OUR CHALLENGE

Functional testing • is necessary• is time consuming• can be ambiguous

Thorough testing cycle (each software not deployed without testing).

3 months: April – June (One window a year to achieve this).

• Lack of agility in responding to new releases, due to the testing time that we need to devote to a release.

• Needed to lock in to a release at a particular time.• Spread the load across the team in terms of manual testing.

Page 7: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

OUR CHALLENGE

Functional testing • is necessary• is time consuming• can be ambiguous

Automated testing is• consistent• easily repeatable• reusable

Thorough testing cycle (each software not deployed without testing).

3 months: April – June (One window a year to achieve this).

• Lack of agility in responding to new releases, due to the testing time that we need to devote to a release.

• Needed to lock in to a release at a particular time.• Spread the load across the team in terms of manual testing.

Page 8: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

ORGANISING TESTS

Page 9: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

RECORDING SCRIPTS

Tests

Command

Target (Locator)

Value

Speed

Page 10: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

EXAMPLE SCRIPT

2_LoginTestStudentAccount

open https://vle.york.ac.uk/webapps/login/?action=relogin

type id=user_id studtesta

type id=password ********

clickAndWait css=input[name="login"]

Page 11: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

TEST MANAGER

Page 12: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

TEST MANAGER

Page 13: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

CONSTRUCTING GOOD TESTS

A good test– Mirror user behaviour– Independent– Report accurately

HTML present? Text present? Screenshot

Page 14: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

SOURCE CONTROL

TEST SCRIPT (A1.3) ADD BLOG POST (ROLE STUDENT)

BLOCK 1 Login as test student

BLOCK 2 Navigate to the test course site

BLOCK 3 Navigate the left hand menu to access the blog tool

NEW SCRIPT Enter the blog and click the Add New Entry button

BLOCK 4 Add content to the content editor

BLOCK 5 Click the submit button

BLOCK 6 Take a screenshot for human inspection/verification

NEW SCRIPT Verify text on the page is present

BLOCK 7 Logout of the VLE

Page 15: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

RUNNING THE PROCESS

Pass

Pass pending check

Fail

Test Script IDExecute

Test Suite

Test Results Web Service

Test Manager Results

Page 16: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

TEST CASES & RUNS

Case = Browser/Platform combination

Run = Results against a particular case

Page 17: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

TEST RESULTS

Page 18: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

PROS AND CONS

Saved time Maintenance burden

Reusable Human intervention

Page 19: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

TAKING THIS FORWARD

• Automate more• Maintenance• Continuous testing• Load testing• Blackboard client assisted testing?

Page 20: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

OUR RESULTS

• 50% of tests automated (from 2013 testing cycle)

• 2014 Upgrade locking into SP16

• How much maintenance is needed, BB switch from iframe’s to HTML5 will impact on this.

• Can we extend the current % of automated tests

• Review this summer of complete process

Page 21: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

DO THIS NEXT

Think about how the adoption of automated testing processes might benefit your institution.

Jointly (with Blackboard) could we come up with a solution to better help the testing processes within our own institutions.

Page 22: IMPLEMENTING AUTOMATED TESTING – WORKING SMARTER NOT HARDER

THANK YOU!

Blayn ParkinsonE-Learning & training Support AssistantUniversity of York (UK)[email protected]

Link to the paper:http://goo.gl/Cp17CL


Related Documents