Automation, Automation Framework, Java, Java Class, javaScript, Selenium, Testing, Web Automation

JavaScript elements handling in selenium

As we see most of the applications are moving towards development with Angular, React, Aurelia, JS, TS bases scripting language and framework which uses these scripting languages.

When it comes to Quality assurance there is still some project which has not adopted a new framework based on these scripting languages.

For those, we have to interact with the JavaScript element multiple times just to make a tweak in the code. As DOM is very responsive and GUI is fragile we need to make those adjustments in the code. Here are some ways via which we can carry out that in a project which uses Selenium and Java together.

Continue reading “JavaScript elements handling in selenium”

Automation, BDD, Behaviour Driven Development, cucumber, gherkin, npm, protractor, Selenium

Implementing page object model using protractor and typescript

Before we dwell on some facts let us step back and understand why I am actually writing this blog. As we understand with this rapid growth not only the developers but we Automation Test Engineers are also constantly grooming ourselves by learning new stuff.

Be it a new programming language or a scripting language we have to widen our thoughts. So while thinking of creating a new automation framework now we are discussing things like handling promises, synchronization, infrastructures, continuous testing, continuous integration, version control, etc

In one of the recent project, I have created a framework in which we picked new tech stack in contrast to the one which is widely used (Yes, I am talking about Java+ Eclipse + TestNg.)

Let’s go deep dive and understand what all I have done for automating an application for which Frontend is written in Aurelia and Backend in C#

Continue reading “Implementing page object model using protractor and typescript”

Automation, Automation Framework, Design Pattern, Design patterns, Page Object Model, Testing, Web Automation

Part II – One step deeper into Page Object Model.

As we have already discussed in my last post on page object model, why we need design patterns while coding. In this post, lets see what all pre-requisites are required to get a quick start so that we can get a better understanding of POM aka Page Object Model:

  1. The functionality classes (PageObjects) represent a reasoned common lineage between the pages of the application.
  2. The Page Object pattern act for the screens of your web app as a sequence of objects.
  3. It encapsulates the characteristics represented by a page.
  4. It permit us to mock-up the UI in our tests.
  5. A page object is an object-oriented class that work as an interface to a page of your AUT.

Continue reading “Part II – One step deeper into Page Object Model.”

Automation, Automation Framework, protractor, Selenium, Selenium Webdriver, Web Automation

TS issue with Circular dependency

TypeError: Class extends value undefined is not a function or null

Continue reading “TS issue with Circular dependency”

Automation, Automation Framework, eclipse, Java, Maven, Page Object Model, Selenium, Web Automation

Maven : Know-how !

To build the Enterprise Edition applications we use Maven.

Please download and install Maven. The build is tested with version 2.2.1 and 2.0.9.

The maven build should be able to set up the sources out of the box. The build should construct all components of the application (e.g. Java Archives, Web application archives, Flex application, etc.) automatically and consolidate them to deployable packages.
Continue reading “Maven : Know-how !”

Agile Testing, Automation, Automation Framework, npm, Testing, Uncategorized, Web Automation, Web Testing

Beautification of console with npm dependency

While submitting a paper in one of the conference I have observed that its not just the code which they see while accepting the submission, but also the efforts you have added to show that the code has different elements which makes it unique And I am not talking about the DS, dynamic programming concepts which are by no choice are important and shall be considered while creating a framework. I will discussing in this post about a console beautification dependency of which can be added to project in very less time and presents a very beautiful welcome note before of the run. This can be a simple and quick add on to your framework, so I thought of adding the same in my project as well.

Continue reading “Beautification of console with npm dependency”
Assertions, Automation, Automation Framework, protractor, soft-assertions, Testing, typescript, Uncategorized, Web Automation

Soft assertions in protractor based typescript automation framework

How many of us has seen that while running code at once glance if the code fails at some step, then other test steps which meant to run post that step is marked as skipped in the final result?

Also, how about rephrasing the same sentence such that the code does not run and marked as skipped in the final run-results challenging the law of ‘fail-fast’. By the execution, we can not infer whether the code was wrong or the functionality dint work as it was an incomplete run for the one who ran it. I am sure many of the QA folks can relate to this. To be more precise, can we relate to this console screenshot.