Responsibilities & Qualities of a Lead Automation Test Engineer

Responsibilities & Qualities of a Lead Automation Test Engineer are:
The Senior Test Automation Engineer will lead the effort to build new test frameworks and or extend existing frameworks. The tool/s accommodates both functional and load testing. These frameworks allow us to perform end-to-end testing in multi-component environments. He will working with the test engineers to design and develop a reusable architecture for the test automation. The Framework or Automation Architecture should consists the following:

Responsibilities & Qualities of an Automation Test Engineer

Responsibilities for Automation Test Consultants may include:
* Establish an automated test environment for UI and non-UI testing
* Review test cases and automate whenever possible
* Educate team members on test automation and drive adoption
* Integrate automated test cases into nightly build system
* Design, document, manage and execute test cases, sets, and suites
* Work in cross-functional project teams that include Development, Marketing, Usability, Software Quality Assurance, Customer Learning, and Support.

Challenging Test Automation Questions – Judge Yourself

1. Our software designers use UML for modelling applications. Based on their use cases, we would like to plan a test strategy. Do you agree with this approach or would this mean more effort for the testers?

Load/Performance Testing Limitations with Manual Testing

Have you ever tried to test performance testing manually? or Are you performing load testing manually? Do you know its drawbacks? If you doing load/performance testing manually then it might let costly failures of Mission-critical applications.

LoadRunner Tips

Note – These tips are very helpful. most of them are taken from

1. To get the password of an auto-generated lr_decrypt() function:
char * password;
web_set_user("2testuser", lr_decrypt("41754c8245221983220368db"),"");

2. Problem Description: How to capture the total bytes of a request/response from the server

Solution: Use the web_get_int_property function
In VuGen 8.1, there are additional options available for the web_get_int_property function like HTTP_INFO_TOTAL_REQUEST_STAT and HTTP_INFO_TOTAL_RESPONSE_STAT. These options return the accumulative size (including header and body) of requests and responses.
Related articles that may be of interest:
Problem ID 29810 - How to verify the size of the last download in bytes
Problem ID 23220 - How to capture HTTP return code information

Record on LoadRunner’s VuGen using a QTP script - Automation testing Tip

1. Bring up VuGen. Create a New script selecting Web (HTTP/HTML) protocol.

2. Start record button.

3. Then, bring up QTP and make sure the option on “Record and Run Settings” dialog be with– Record and Run test on any Open web browser, radio button.

4. Start ‘Record’ on QTP and perform the user activities on the browser invoked by the VuGen.

5. Both VuGen and QTP would record the actions on their interfaces.

This way we can make sure the VuGen to record the same sequence of user actions/events by ‘Replaying’ the QTP recorded script, after a browser is initiated by the VuGen’s recording engine.

Tester’s Mental Life

 Software Tester Mental Life
Boris Beizer, identified five phases of a tester’s mental life:
Phase 0: There’s no difference between testing and debugging. Other than in support of debugging, testing has no purpose.
Phase 0 Thinking: Testing = Debugging.

Automation Testing LifeCycle/Process Simplified

Automation Testing LifeCycle
Phase Activities Outcome
Planning Create high level test plan Test plan, Refined Specification
Analysis Create detailed test plan, Functional Validation Matrix, test cases Revised Test Plan, Functional validation matrix, test cases
Design test cases are revised; select which test cases to automate revised test cases, test data sets, sets, risk assessment sheet
Construction scripting of test cases to automate, test procedures/Scripts, Drivers, test results, Bug Reports.
Testing cycles complete testing cycles Test results, Bug Reports
Final testing execute remaining stress and performance tests, complete documentation Test results and different metrics on test efforts
Post implementation (See Post Project Reviews in testing) Evaluate testing processes Plan for improvement of testing process

Guidelines/Best Practices for effective Software Test Planning – Part 2

Test Plan First

Following are the guidelines/best practices for effective test planning:
  • Identify the requirements to be tested. All test cases shall be derived using the current Design Specification.

Purpose & Advantages of Test Plan

 Test Plan First



  • The test plan keeps track of possible tests that will be run on the system after coding.
  • The test plan is a document that develops as the project is being developed.
  • Record tests as they come up
  • Test error prone parts of software development.
  • The initial test plan is abstract and the final test plan is concrete.
  • The initial test plan contains high level ideas about testing the system without getting into the details of exact test cases.
  • The most important test cases come from the requirements of the system.
  • When the system is in the design stage, the initial tests can be refined a little.
  • During the detailed design or coding phase, exact test cases start to materialize.
  • After coding, the test points are all identified and the entire test plan is exercised on the software.

Purpose of Software Test Plan:

  • Test Plan Ensures all Functional and Design Requirements are implemented as specified in the documentation.
  • To provide a procedure for Unit and System Testing.
  • To identify the documentation process for Unit and System Testing.
  • To identify the test methods for Unit and System Testing.

Advantages of test plan

  • Serves as a guide to testing throughout the development.
  • We only need to define test points during the testing phase.
  • Serves as a valuable record of what testing was done.
  • The entire test plan can be reused if regression testing is done later on.
  • The test plan itself could have defects just like software!
In software testing, a test plan gives detailed testing information regarding an upcoming testing effort, including
  • Scope of testing
  • Schedule
  • Test Deliverables
  • Release Criteria
  • Risks and Contingencies

Test Plan Preparation Guidelines – Part 1

The software test plan is the primary means by which software testers communicate to the product development team what they intend to do. The purpose of the software test plan is to prescribe the scope, approach, resource, and schedule of the testing activities. To identify the items being tested, the features to be tested, the testing tasks to be preformed, the personnel responsible for each task, and the risks associated with the plan.
The test plan is simply a by-product of the detailed planning process that’s undertaken to create it. It’s the planning that matters, not the resulting documents. The ultimate goal of the test planning process is communicating the software test team’s intent, its expectations, and its understanding of the testing that’s to be performed.

Classic Test Automation Mistakes

There are many good reasons to start automation. But sometimes – Companies start automation testing with enthusiasm but end up with manual testing only. Below are 5 mistakes that management might do while implementing automation:

QTP Automation Object Model Simplified | QTP AOM

We received couple of queries on QTP AOM. In this post we simplified the QTP AOM, so that a newbie in QTP can also understand what is Automation Object Model and how it works.

Rate Yourself in Software Testing | Skills of a Professional Tester | Lets become Test Professional from Test Dummies.

Today employers want test professionals – not test dummies. There are unique skills of testers that are highly desired by employers to make the testing process more efficient and effective. See the checklist for a cross-section of the desirable skills of a test professional

Effective Practical Test Reporting Tips & Techniques | Software Testing Summary Reports Generation

Testing is very important phase in the Life Cycle of Software Development so whatever the work testers and test lead are doing in this Phase it should be properly documented and testers should be able to provide the needful information in proper Reports. Here are some important documents, their frequency and the reason for those documents have a look at it:

Tips to Prioritizing the tests | A way to achieve Time-boxing in testing

A common problem is faced in testing phases (especially when UAT/release is near) - There are so many tests for testing/execution but there is so less time. In 2004, Johanna Rothman gives a recipe in her article "So Many Tests, So Little Time
| TimeBox the testing". From Johanna’s article, I conclude that Prioritizing the tests is one important step to achieve time-boxing in testing.

For those who don’t know what is time-boxing:
Time-boxing is a well-established project management (time management technique) used to limit project scope in a fixed duration by forcing tradeoffs. Time-boxing is a valuable technique for testing as well. For example you need to test the application before UAT and there are only 4 weeks left.