Triaged Tester

March 12, 2009

Automation workflow

Filed under: Automation,Tips — Triaged Tester @ 6:25 am

Automation Workflow


March 11, 2009

How to Implement Test Automation Framework Methodology

Filed under: Automation,Checklist,Stratergies,Tips — Triaged Tester @ 6:10 am
Tags: , ,

1.Identification of the Scope of Testing: Company Oriented, Product Oriented, Project Oriented
2.Identification of the Needs of Testing: Identify Types of testing e.g. FT, Web Services etc. and application / modules to be tested.
3.Identification of the Requirements of Testing: Find out the Nature of Requirements, Identification of type of actions for each requirement & identification of High Priority Requirements
4.Evaluation of the Test Automation Tool: Preparation of Evaluation Checklist, Identification of the Candidate Tools Available, Sample Run, Rate & Select the Tool, Implementation & Training
5.Identification of the Actions to be automated: Actions, Validations & Requirements supported by the Tool
6.Design of the Test Automation Framework: Framework Guidelines, Validations, Actions Involved, Systems Involved, Tool Extensibility Support, Customs Messages & UML Documentation
7.Design of the Input Data Bank: Identification of Types of Input file, Categorization & Design of File Prototypes
8.Development of the Automation Framework: Development of Script based upon Framework Design, Driver Scripts, Worker Scripts, Record / Playback, Screen / Window / Transaction, Action / Keyword & Data Driven
9.Population of Input Data Bank: Different Types of Data Input, Population of Data from Different Data Sources, Manual Input of Data and Parent – Child Data Hierarchy
10.Configuration of the Schedulers: Identify Scheduler Requirements & Configure the Schedulers.

March 10, 2009

Performance counter – 4

Filed under: Performance,Tips — Triaged Tester @ 1:24 pm
Tags: ,

Additional web counters  to monitor performance

ASP.NET -> Request Execution Time    Bear in mind that this is only the time it took to execute the mos recent request.
ASP.NET -> Requests Current    Total of waiting and executing requests.
ASP.NET -> Request Wait Time    If wait time is going up and CPU is low then opening up the threading options will probably help.  This could also indicate the need to additional hardware to hand the load.
ASP.NET -> Requests Queued     
ASP.NET Apps -> Pipeline Instance Count  Make sure this is for the Web Service App Only on thread at time can use a Pipelin instance.  So a sudden increase can indicate backend latency.
ASP.NET Apps -> Requests Executing  Make sure this is for the Web Service App  
ASP.NET Apps -> Requests Total  Make sure this is for the Web Service App  
ASP.NET Apps -> Requests/sec Make sure this is for the Web Service App How quickly are we handling requests?

March 9, 2009

Recommended tools

Filed under: Automation,Checklist,Guidelines,Tips,Tool — Triaged Tester @ 1:23 pm
Tags: ,
Functionality Description Representative Tools
Functional Testing Record and Playback tools with scripting support aid in automating the functional testing of online applications  Win Runner, Rational Robot, Silk Test and QA Run. Tools like CA-Verify can be used in the m/f environment
Test Management  Management the test effort  Test Director
Test Coverage Analyzer Reports from the tool provide data on coverage per unit like Function, Program, and Application Rational Pure Coverage 
File Comparators  Verify regression test results (by comparison of results from original and changed applications). Comparex (from Sterling Software)
Load Testing  Performance and scalability testing Load Runner, Performance Studio, Silk Performer and QA Load
Run-time error checking Detect hard to find run-time errors, memory leaks, etc. Rational Purify
Debugging tools  Simplify isolation and fixing of errors Xpediter,  ViaSoft (Mainframe applications), VisualAge debuggers and many other debuggers that come with development kits. 
Test Bed Generator Tools aid in preparing test data by analyzing program flows and conditional statements CA-Datamacs

March 6, 2009

Choosing what to automate

Filed under: Automation,Tips — Triaged Tester @ 1:22 pm
Tags: ,

Most, but not all, types of tests can be automated. Certain types of tests like user comprehension tests, tests that run only once, and tests that require constant human intervention are usually not worth the investment to automate. The following are examples of criteria that can be used to identify tests that are prime candidates for automation.

High Path Frequency – Automated testing can be used to verify the performance of application paths that are used with a high degree of frequency when the software is running in full production.  Examples include: creating customer records, invoicing and other high volume activities where software failures would occur frequently.

Critical Business Processes – In many situations, software applications can literally define or control the core of a company’s business. If the application fails, the company can face extreme disruptions in critical operations. Mission-critical processes are prime candidates for automated testing. Examples include: financial month-end closings, production planning, sales order entry and other core activities.  Any application with a high-degree of risk associated with a failure is a good candidate for test automation.

Repetitive Testing – If a testing procedure can be reused many times, it is also a prime candidate for automation. For example, common outline files can be created to establish a testing session, close a testing session and apply testing values. These automated modules can be used again and again without having to rebuild the test scripts. This modular approach saves time and money when compared to creating a new end-to-end script for each and every test.

Applications with a Long Life Span – If an application is planned to be in production for a long period of time, the greater the benefits are from automation

« Previous PageNext Page »

Create a free website or blog at