15
Lessons Learned The Challenges and Successes of Integrating Automated Testing into Existing Development Projects

Lessons Learned: The Challenges and Successes of Integrating Automated Testing into Existing Development Projects

Embed Size (px)

Citation preview

Lessons Learned

The Challenges and Successes of Integrating Automated Testing into Existing Development Projects

Who Am I?

• Software Tester for 16 Years, Manual and Automated

• Worked in a variety of industries

• Been using SmartBear TestComplete product since version 1.52 (called AQTest)

• Never been part of a “green fields” project for test automation

1

Lessons Learned

Soft Skills

Non-Technical lessons for the technical person

Lessons Learned

Page

Manage Expectations

• Won’t “fix” everything

• Different than Manual Testing

• Takes Investment before benefit is realized

Lessons Learned

Page

Manage Expectations

• Clearly communicate benefits

• “No one’s job will be replaced”

• Recruit “partners”

Lessons Learned

Page

Know Your Team Skill-Set

• Coding skill – Not everyone has it

• Desire – Not everyone wants it

• Manual Testers are still needed; Can adviseautomation efforts

Lessons Learned

Page

Know Your Team Skill-Set

• Experience with automation tools

• Writing Code vs. WYSIWYG editor (Keyword Testing)

• Different levels of coding skill

Lessons Learned

Tool Skills

Best practices learned in the crucible

Lessons Learned

Page

Design a Framework

• Implementing a framework later costs resource

• Allows to build something that meets short term andlong term needs

• Considers team skill-set

• TestComplete allows for building a variety offramework structures

Lessons Learned

Page

Design a Framework

Lessons Learned

‒ Execution of tests driven

by a data source instead

of code

‒ Centralization of test

execution outside of the

tool

‒ Allows non-automation

staff to execute tests

Data driven structure works

best

‒ Utilizes an SQL backend

‒ Uses Script extensions

for ease of test

implementation

‒ Built in external

reporting from SQL

‒ The Framework should

meet the need

Current Framework Key Point

Page

Design a Framework

Lessons Learned

Table-Driven Framework

https://bitbucket.org/tristaanogre/tabledrivenframework

Page

Use the Tool (TestComplete)

• Don’t reinvent the wheel – NameMapping vs. customcode

• Record/Playback – Not a useless feature

• Checkpoints are your friend

Lessons Learned

Page

Use the Tool (TestComplete)

• Completely under utilized

• Open Architecture allows for infinite extensibility

• Resolves many issues of shared code across projects

• Experienced staff create extensions for lessexperienced staff to use

Lessons Learned

Any Questions?

Thank you!