Teledyne ISCO Automated Software Testing

subduedlockΜηχανική

5 Νοε 2013 (πριν από 4 χρόνια και 2 μέρες)

107 εμφανίσεις

Teledyne ISCO | CONFIDENTIAL

Teledyne ISCO Automated Software Testing

Teledyne ISCO

| CONFIDENTIAL

Agenda

Future Automation Testing

Automation Vs Manual Efforts

Introduction

Current Automation Status

Q & A

Teledyne ISCO

| CONFIDENTIAL

Introduction

Use of an Automated System for Testing Software


Tool: Mercury Automated Software Testing System


Tests Software by automatically running software based on a script.


Logs discrepancies (errors) in execution


Used on our Flowlink Product


Fairly Large program


Gui contains 5000 text lines


Development at three sites
-

Offshore, Outside, and In
-
house


Need to Verify Existing Functionality as new Features are added



Teledyne ISCO

| CONFIDENTIAL

Introduction (continued)



Automation Status


Manual Vs Automation Efforts


Time Saving


Resource Saving


More Test Coverage


Better product


Future Automation Testing Approach



Teledyne ISCO

| CONFIDENTIAL

Current Automation Progress

Automation Scripts Development as of 8/30/2007

Device Series

Device Name

Number of Scripts


4200

4250

50

4210

50

4100

4150 + Rain

44



2100

2150 Itself

32

2150 + 2110 + 2103c

52

2150 + 2102

32

2103 + 2150 + 2108

37


6712

6712+750

18

6712+730

18

Total =

333


Streamlined the manual test scenarios for the devices 4100’s,4200’s,6700’s and 2100’s


Designed and documented the automation framework for Flowlink


Created and documented automation scripts for the devices 4100’s,4200’s,6700’s and 2100’s


Executed automation scripts for the devices 4100’s,4200’s,6700’s and 2100’s


Created Single Framework folder for all devices 4100’s,4200’s,6700’s and 2100’s


Automation scripts transition to Flowlink test team


Non
-
language specific scripts. Creation of additional data files and object repositories

Teledyne ISCO

| CONFIDENTIAL

Manual Vs Automation Efforts


Device
Series


Releases


Total Scripts
Executed

Manual

Automation

Time

Saving

# of Hours Required
to Execute

# of Hours Required
to Execute

4200,4100,
2100,6712

Oct 2007

1766

580 Hours

90 Hours

490 Hours

Automation Execution Efforts as of 8/30/2007

Automation Vs Manual
-

Time Saving as of 8/30/2007

Device
Series

Device Name

# of Builds

# of Test Scripts
executed

Total Scripts
Executed


4200

4250

12

50

600

4210

12

50

600

4100

4150 + Rain

3

44

132



2100

2150 Itself

2

30

60

2150 + 2110 + 2103c

2

50

100

2150 + 2102

2

30

60

2103 + 2150 + 2108

2

35

70


6700

6712+750

4

18

72

6712+730

4

18

72

Total =

325

1766

Cont…

Teledyne ISCO

| CONFIDENTIAL

Current Automation Progress


Unit Tests


Generate unit tests for newly developed code


Tests sections of code at build time


Focuses on base level of code


Over 1,300 unit tests implemented


Notification if automated builds fail


Teledyne ISCO

| CONFIDENTIAL

Manual Vs Automation Efforts

Automation Vs Manual
-

Test Coverage as of 8/30/2007


Automation scripts are testing multiple combinations and scenarios of the Flowlink
application which were not regularly tested.


Found several defects during automation scripts execution

Automation Vs Manual
-

Resource Saving as of 8/30/2007


To execute 1766 test cases Manually 72 Man
-
Days are required


To execute 1766 automation scripts 12 Man
-
Days are required


Addition to the above point, automation scripts are standalone and unattendable

Teledyne ISCO

| CONFIDENTIAL

Automation Testing Approach

Phase1


All functionality automation for one device 4250


Goal:
Automate maximum functionalities on device 4250 and design this automation

suite as base model for other devices.


Duration:
9 weeks (3/15/07 to 5/18/2007):
Completed


Activities:


Streamline the manual test scenarios on device 4250


Design and document the test automation framework for Flowlink application


Create and document automation scripts for device 4250


Execute automation scripts for device 4250


Automation scripts transition to Flowlink test team


Responsibility


Ramesh Ravi

Teledyne ISCO

| CONFIDENTIAL

Automation Testing Approach

Phase2


Major/Critical functionality automation for all devices


Goal:
Automate Major/Critical functionality test scenarios for all devices which will

execute on each build to verify the build breaks or show stoppers (Formally called

smoke test)


Duration:
Start 5/18/07 End 11/23/07 : In Process


Activities:


Streamline the manual test scenarios for different devices


Reuse the existing automation suite and create automation scripts for different devices


Execute automation scripts for different devices


Responsibility


Ramesh Ravi & Flowlink test team




Teledyne ISCO

| CONFIDENTIAL

Automation Testing Approach

Phase3


Core Regression functionality automation for all
devices


Goal:
Automate all functionalities for all devices which will execute on each
build.


Duration:
<TBD>


Activities:


Streamline the manual test scenarios for different devices


Reuse the existing automation suite and create automation scripts for
different devices


Execute automation scripts for
different devices


Responsibility


Flowlink test team

Teledyne ISCO

| CONFIDENTIAL


Future Plans and Possibilities


Unit testing


Testing Subsystems or modules after changes


Application to Embedded Systems

Teledyne ISCO

| CONFIDENTIAL

Q & A