UK Tester Forums

Dear Paul Rolfe ,

Thinksoft Global Services invites you to discover how as a specialist Thinksoft provides Quality Assurance Services and addresses the different aspects of test automation through the innovative Automation Test Lab

Let’s learn from each other and network with professionals. We welcome you to be a part of this collaboration of experts. Date: October 19, 2011
Time: 2:30 pm
Venue: Farringdon Room, St.
Bride Foundation, Bride Lane,
Fleet Street, London EC4Y 8EQ

Focus:

We are using HP Quality Center for our test management tool, and all of our manual tests are created and executed in this. For test automation our vendor test specialists use QTP with a proprietary framework, that integrates with Quality Center.

1 Manual test creation productivity is 10 tests/person/day.
2.Automated test creation productivity is 1 test / person / day, using QTP with the framework. Is this a reasonable productivity level? - What would you expect it to be?
3.Are there any open source frameworks that could be used with QTP and QC to improve productivity?

I'm about to set up a two day test automation event week of 11th October with an expert from Europe however rather than try and second guess what people want to learn about test automation I thought I would ask the community and the UK TMF is my first port of call since I think I'll get some sensible suggestions.

Please add your suggestions to this forum or contact me directly.

Here are my thoughts & ideas:

Do you need to learn how to make a business case for tools?

An Automation Framework primarily comprises of elements like:

A) Function Library
B) Object Repository
C) Database
D) Application Scenario Files
E) Initialization VB Script
F) Sequence File
G) Driver Script
H) Test Case List File

A) Function Library:
While creating automation framework the entire coding is done by using VB script functions that are user defined. We store these VB script functions in function library files with (*.vbs) extension. Apart from Driver Scripts, there is no need of doing any script creation beyond the function library.

Suggest a rewrite of this section as follows...

Tools can be classified by:

• Functionality (as per Foundation)
• The role that uses them (used in this course)
• Test level supported by what level of testing is performed (component, integration, system, acceptance)
• Specific risks they are meant to address
• Tools specific to certain domains, e.g. traffic simulation & signaling, networks, protocol, transactions, TV-screens, expert systems
• Test supporting data, environment, configuration management etc.

Suggest a rewrite as follows ...

Often, testers and developers create tools or utilities to address specific problems. Maybe a tool isn’t available or available in your environment. These tools are often valuable, but are often only usable by their author. If the tools have value and you are dependent on them, spread the word, get others to use them.

Get the author to draft a user guide, Wiki or Blog to help others, but take care that tool building doesn’t overtake the cost of buying.

Tools used to test safety critical systems must be certified to comply with the intended purpose against the corresponding standards.

what standards? Specify.

This is true of all tools, not just open source.

It is not recommended to use open-source tools in safety-critical systems, unless they have obtained the appropriate level of certification.

This is true of all tools, not just open source.