Untitled-1

Achieve Quality Code and ROI through Test Automation

By:  TAGS: ,

Software development companies are under constant pressure to deliver new applications that will satisfy every user’s needs across all devices and locations, preferably at high speed and low cost. Automated testing has become a way to ensure applications are error-free, cost-efficient, and quickly delivered.

Automated testing takes place on several levels of the project:

  1. Unit testing:  Usually performed by developers, the main goal of these tests is to make sure that the app’s components match in terms of functional requirements. For example, a unit test could involve an OOP class or function.

  2. Component testing:  Usually performed by developers, the “component” being tested is a part of the high-coupled logic. For example, authorization, payment processing, and order submission could all be components.

  3. Read More
shutterstock_234022315-min

Testing Generated Binary Files with RSpec

By:  TAGS: , DATE: 09/21/2017

RSpec has become the standard framework used to test code written in Ruby. Its extensive library allows developers to isolate, extract, and test specific files within an application in order to decrease bugs and improve overall quality and stability. Although RSpec provides the tools necessary to test virtually every aspect of an application, some developers may not be familiar with certain time-saving techniques that can be applied during the testing process. This article focuses on using RSpec to generate and then test PDF, XLS, or any other binary files from a Rails application.

Read More

Untitled-1

Emulating Long Life Cycles during Automated Testing

By:  TAGS: , , DATE: 10/19/2017

Automated testing has become standard industry practice, saving quality assurance engineers the time and effort required of manual testing while enhancing overall code efficiency and accuracy. It also allows companies to reduce costs while speeding up product release times. These benefits can become especially apparent when developers are testing web applications that have long life cycles like those in the financial industry.

When working on these continuously expanding projects, SDETs (Software Development Engineers in Test) must implement the testing infrastructure and automated tests in such a way that the state of the system can be checked at certain designated intervals. In a sense, these engineers must travel in virtual time. This process can be quite complex and problematic. To avoid testing-related issues when working on projects with long life cycles, SDETs can follow several approaches as detailed in this article. These approaches are implemented in Ruby, but they can easily be converted to any programming language.

Read More

< All Categories