preload

Advertising

Recent Posts

Web Accessibility: Impairment ...

Posted by Albert Gareev on Sep 18, 2014
The recent WTA session we performed prompted me that there are a lot of materials I can share with regards to Accessibility Testing. I created them while learning it for myself, using various Web resources. I begin with ...

WTA54: An Intro To Accessibility Testing

Posted by Albert Gareev on Sep 16, 2014
After somewhat a pause, I’m stepping back in as a facilitator in Weekend Testing Americas chapter. The good occasion was recent session on Web Accessibility, initiated by Michael Larsen. This is the area I’m actively ...

Accessibility Testing with WAVE Toolbar

Posted by Albert Gareev on Sep 10, 2014
Preface If you have just installed WAVE toolbar, the variety of available commands for sure looks overwhelming. And, frankly, professional Accessibility testing requires specialized knowledge and exploratory testing skills. ...

GUI Automation Components

Posted by Albert Gareev on Sep 09, 2014
To perform testing, GUI automation scripts need to encapsulate the following components: Test data, used for input and verification. Service functionalities, like reporting, data retrieval, etc. GUI mapping – set of logical ...

Scalability

Posted by Albert Gareev on Aug 29, 2014
Scalability is an integral characteristic comprising the following: How well volume of test cases can be extended without linear (or even geometric) growth of efforts for creation and maintenance. How well the same testing ...

Maintainability

Posted by Albert Gareev on Aug 22, 2014
Maintainability is an integral characteristic comprising the following: Updates in test logic and/or GUI mapping caused by the changes in the application under test. Design or refactoring of automation for the purpose of ...

Reliability – Performance

Posted by Albert Gareev on Aug 15, 2014
Performance of automated tests must be optimized by design and implementation, to achieve best coverage in shortest time possible within the constraints of the context. This should be achieved by use of configurable ...

Reliability – Attendance and ...

Posted by Albert Gareev on Aug 08, 2014
Attendance Automated tests must be designed for unattended execution. Failure criteria: Test script may stop or break execution at any moment. Manual action required to continue the execution. Full restart is required if ...

Reliability – Operation

Posted by Albert Gareev on Aug 01, 2014
Automated tests must be delivered as a software product which can be used (operated) by testers and other team members without special technical skills in programming or automation tools. Operation requirements for all setup and ...

Business Value – Usability

Posted by Albert Gareev on Jul 25, 2014
Automated tests, as a product, should be available for use by any tester (and other team members) with minimal technical skills required.   This requirement heavily applies to the following procedures: Automation setup ...

Business Value – Transparency

Posted by Albert Gareev on Jul 18, 2014
Transparency of coverage should include written information about the following: Implemented Test Coverage – coverage of each and every automated test case, including test purpose and main execution steps. Executed Test ...

Business Value – Creation Effort

Posted by Albert Gareev on Jul 11, 2014
Creation effort maps directly to costs – one can compare creation expenses with potential savings. Creation effort is an integral characteristic comprising the following: Test design or re-design of manual test cases to ...

Business Value – Verification ...

Posted by Albert Gareev on Jul 04, 2014
The automation is fundamentally limited to mechanical verification (aka Checking) – through comparison of values only. However, with proper design, automation may simulate many of usage scenarios, which will trigger possible ...

My look at requirements

Posted by Albert Gareev on Jul 02, 2014
With years of my career evolution as a testing and automation professional, I’ve developed my own practical view about requirements, their role, and how to deal with them in a context-driven, heuristic way. I’m ...

Business Value – Purpose

Posted by Albert Gareev on Jun 27, 2014
By industry standard definitions, test automation is created with the purpose of extending coverage, saving in test execution time, allowing for increase of test iterations, earlier detection of defects, and everything ...

Automation Requirements, Revisited ...

Posted by Albert Gareev on Jun 24, 2014
As I’m finding myself, I’ve been writing about QA Test Automation quite extensively in the years around 2010. No surprise – it was my main specialty. Then I was extending and sharpening my skillset in the field ...

Beware of Rapid Software Testing

Posted by Albert Gareev on Jun 10, 2014
Let my story be a warning. About 4 years ago, being a successful test automation engineer, I felt strong enough to challenge James Bach and Michael Bolton, who were loudly advocating for exploratory testing approach and, ...

AppendChildElements (QTP, TestComplete, ...

Posted by Albert Gareev on Feb 10, 2014
Parent page: Service Functions – MSXMLDOM (QTP, TestComplete, VBScript) Description Append all child elements from the list (including their attributes, comments, text nodes) to XML node. Implementation Public Function ...

Best practices of scripted testing

Posted by Albert Gareev on Dec 10, 2013
One “QA” reads a document how the application is going to be. To say better, it’s a writing of someone’s beliefs how certain, those explicitly described, aspects of an application should be according to ...

Whirlpool Testing

Posted by Albert Gareev on Sep 23, 2013
Agile Testing? Waterfall Testing? Here’s another cool name I invented. In case good old Exploratory Testing doesn’t sound cool to you :) PS. I guess, the picture speaks for itself. This is a slide from my presentation ...
Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported
This work by Albert Gareev is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported.