Articles

A few months back, I was going through some posts related to Test Automation in Quora. Suddenly a question posted by an anonymous user caught my attention – “What is Maven in Selenium?”

This was not the first time I came across this question or similar questions during my journey as an SDET. This is quite common since there is a lot of confusion regarding the differences between the build automation tools (“Maven” is one of them), and the test automation libraries, mostly among the testers who have just started learning/working on test automation and came across build tools for the first time.

Source de l’article sur DZONE

A few weeks ago I had some interesting debates on the projects I work on, on questions like:

  • Is the automation engineer a developer?
  • Is a developer the best candidate to be an automation engineer? 
  • Where does the good ol’ Software Engineer in Test (SET, a.k.a SDET) fit in this fierce new world full of code and dependencies? 

It seems that the trend nowadays when looking for job candidates in automation is that they need to have the skills of a programmer. I have been doing technical interviews for people who are running for Test Engineer positions for years, and this trend has been increasing more and more. That is why I give the same advice to anyone asking me how to get into the automation world: “Start learning the fundamental concepts of object-oriented programming and how they apply to automation testing.”

Source de l’article sur DZONE

Assertions are an important part of any test automation framework, and Serenity gives us many options. You can, of course, use standard JUnit, Hamcrest or AssertJ assertions at any point in a Screenplay test. But more recent versions of Serenity Screenplay provide an alternative approach, which many developers find easier to use and faster to write: the serenity-ensure module.

Introducing serenity-ensure

The Ensure class produces a Performable, so you can integrate them directly into the attemptsTo() method. It also has a very readable DSL and lets you use code completion to discover the assertions you can use for different values, making writing assertions easier and quicker.

Source de l’article sur DZONE

Before you start: If you don’t know what Katalon Studio is, read this first, and get to know why I picked it to build web automation.

Katalon Studio at a Glance

To be mentioned, before looking at the studio, Katalon project offers an IDE tool for Chrome, called Katalon Recorder. It’s an extension that records actions, captures web elements, plays the automated test case you recorded and speaks Selenese.

Source de l’article sur DZONE

In the current technological era, it is normal to find 4-5 new Android-based apps uploaded to the Play Store every week. Seeing competitors deliver apps so frequently creates pressure to deliver quality apps in a short span of time. During this limited time, mobile application development and testing of the business’ purpose should be achieved. With this pressure, there is a need to automate certain processes which can save time while providing a trusted output.

That being said, mobile test automation can save a lot of time and is always preferred over the entire manual test execution process. With much less effort, the verification of frequent test cases that manual execution requires can be automated, and more effort can be diverted to new features of the application, which are vulnerable and tend to have more defects.

Source de l’article sur DZONE

UI testing is an important part of quality assurance. Specifically, UI testing refers to the practice of testing front-end components to make sure that they do what they’re supposed to. If a user clicks the Login button, the login modal appears. If they click a link, they’re brought to the appropriate part of the application. With automation platforms, these individual tests can be linked together into workflows and automated. Business-driven development style tests can be created in this fashion. The UI can be tested to see that each individual path that a user may take is functional and that the interface is responding appropriately. Other platforms exist that allow these workflows to be tested on simulated resolutions and devices, ensuring that the user experience is consistent across all possible combinations of browser and device.

API testing lives a layer below UI testing. The UI is fed by these APIs and renders the DOM based upon conditions set by both the user and the developer. These conditions determine the sort of API call that’s made to populate the viewport. When we’re UI Testing, it could be argued that we are indirectly testing the API layer. It’s actually pretty fair to say so. Many of the actions that our UI platform will take will issue API calls. If the DOM rerenders correctly, we can assume to an extent that the API call was successful. The dangerous ground here is the assumption.

Source de l’article sur DZONE

We keep hearing about new solutions for test automation and continuous testing. Such solutions aim to increase the test automation authoring as well as the maintenance associated with these tests as the product evolves.

With this trend, many software quality engineers, SDET, and test automation architects are asking themselves whether their job is at risk and what the future holds for them.


Source de l’article sur DZONE (AI)

Pushing the Bounds of What We Can Automate in Software Testing

We have this funny little tagline about how we’re pushing the boundaries of test automation. It’s a simple enough thing when you say it, but what do we really mean by it?

Recently, we were recognized by several industry analysts for the work we’ve been doing pushing those boundaries. At voke, they said, "Parasoft is a company borne of innovation with a relentless focus on software quality," and Forrester said, " Regarding AI, Parasoft has an impressive and concrete roadmap to increase test automation from design to execution, pushing autonomous testing."


Source de l’article sur DZONE (AI)

Over the years a lot has been done to enhance the control and efficiency of application development processes. From Agile development to change management solutions based on ISO and ITIL standards, the progress has been remarkable. However, like everything else, this, too, has a downside. They say that every cloud has a silver lining, but in the world of technology, this silver lining is likely to affect the functionality of the cloud. The increase in the use of Agile development has aggravated the pressure IT organizations face in deploying new applications.

Each new enterprise application brings in several diverse application components spread across numerous environments, including application servers, desktops, Web servers, mobile devices, databases, etc. Also, most large organizations have different departments handling each of these functions, and the potential product users are often not in control of the timelines. Besides, since security and compliance requirements put a lot of burden on the IT teams, companies adopt a "better safe than sorry" approach and discourage employees from easily getting new applications or their versions. For the product vendor, the total cost of support is directly proportional to the number of older versions out there in the field.

Source de l’article sur DZone