Tag: test automation

Using Containerization within Your Test Automation Solution

It was almost destined that test automation engineers would begin to integrate Selenium and Selenium Grid into Docker, which has created a truly unique method of cross-platform testing with far less infrastructure requirements for their CI solution, as well as a lower cost than commercial cloud-based solutions like Saucelabs or Browserstack.

Two rows of Roman arches stacked on each other

How POM-based Architecture Boosts your Automated Testing

Recognizing the enormous effort for performing manual UI testing, organizations have opted to automate their UI test activity to speed up the development pipeline. To make automation payoff, one must approach it with the same mindset that we approach the development of our production code.

Over a black background, golden light streaks in the pattern of an "X" inscribed in a circle

The ‘What’ and ‘Why’ of API Testing

Why do testers need to know how to do API testing?  The short answer: for complete coverage! UI testing, either manual or automated, is still just testing the presentation layers to make sure the end user experience matches expectations and meets functional requirements. So, if solely using UI testing without data-driven API testing, it’s nearly impossible to validate all different possibilities of how a user could manipulate the application and the related sub-applications.  The best approach is to test both UI and API.

test automation engraved on metallic gears with blue sparks shoot off

Treat Test Automation Like a Project

Treating test automation like a project helps to ensure the success of your automation initiative. Applying Agile project principles along with preparing appropriate documentation keeps the automation activities on schedule and produces a maintainable automation solution.


Test Talk: Automation Logging

Logging is an important part of building robust automation testing. In this video, learn what information is logged, how logs are used, and why this is important.

mechanical gears

Why Test Automation is Essential to Successful DevOps

It’s been proven that QA leads to a lower failure rate and ultimately better software, but when deadlines approach and time constraints become an unwelcome reality, QA professionals yearn for a way to lessen the pressure and keep the process flowing.  The natural progression for a DevOps process that is already highly automated is to transition more of the QA process to fall in line, either through test driven development (TDD) or automated scripts running continuously during testing of newly developed features, and onwards as UAT and production environments are smoke tested.

Video blog with play icon over futuristic abstract blue gears

Test Talk: Automation ROI

This video answers questions like, how automation helps reduce the cost of testing, when can you start seeing an ROI from test automation, and what is the best place to get started with automation.


Multi-Layer Frameworks for Test Automation

Legacy test automation systems, whether developed as record-and-playback scripts or coded software, have been designed without reuse in mind. This philosophy runs counter to the modern software architecture principles of code reuse and refactoring. A multi-layered framework maximizes reuse between automation projects for a given combination of automation tools (Microsoft CodedUI, Selenium, rSpec) and programming languages (C#, Java, Ruby).


Testers Shift Left

Testers can bring a testing mindset and skills to build in quality in a software project as compared to testing it in at the backend. Testers, let’s all shift left.

blog testing

The Agile Tester, Converting to Automation

In an Agile process, the velocity of development and churning out releases at the end of every sprint will overwhelm a manual tester without some sort of automation.  If a tester has to manually execute tests for new functions, verify bugs, and run the system through regression every two weeks…the pace will eventually wear the test team members out and cause defects to slip through.  In Agile, poor quality is a small snowball at the top of a powder-covered peak; once the ball starts to roll downhill, gaining size and speed, the odds of bringing it back to the top of the mountain quickly drop to zero.  The only way to stay on track is to take manual tests and automate as much as possible.