Agile, Agile, Extreme Programming, Kanban

Effective Delivery Teams in Agile practice

For an organization to make sure the business is running, as usual, it directly depends on how the employees understand the business. Now the question is, do we as really want them to understand how we run business and what shall happen if we dint meet the EBITA for that matter.

Or in other words, how important for the employees of an organization is to understand what core believes it holds?

Safeguarding the health of each of the delivery teams is a continuous responsibility. It requires teams that are continuously improving on the ever-changing mechanics of the product -employment-client lifecycle.

Continue reading “Effective Delivery Teams in Agile practice”
Agile Testing, Automation, Functional Tests, saucelabs, Scrum, Selenium, smartbear, Testing, Web Testing

Cross browser testing via Sauce labs?

Learning starts when you start experimenting. Be it in Information Technology or layman’s life.

I will be using this space to make you understand a tool which will be of great help, not only for all the Software QA but to the Product Owners, Developer, stakeholders, etc. It has all the solution to the issues we foresee in day-to-day life. As we know in Agile we always define the Acceptance criteria, Definition of Done while make a story.

For those who are not so familiar with Agile , Kindly go through this wiki page- https://en.wikipedia.org/wiki/Agile_software_development.

Continue reading “Cross browser testing via Sauce labs?”

Agile Testing, Browser, Chrome, Exception, protractor, Selenium

protractor- session not created: Chrome version must be between 70 and 73

DevTools listening on ws://127.0.0.1:57284/devtools/browser/f4efc932-01f3-4ac5-8a77-b19e65f2849b
[14:36:42] E/launcher – session not created: Chrome version must be between 70 and 73
(Driver info: chromedriver=2.45.615291 (ec3682e3c9061c10f26ea9e5cdcf3c53f3f74387),platform=Windows NT 10.0.17134 x86_64)
[14:36:42] E/launcher – SessionNotCreatedError: session not created: Chrome version must be between 70 and 73
(Driver info: chromedriver=2.45.615291 (ec3682e3c9061c10f26ea9e5cdcf3c53f3f74387),platform=Windows NT 10.0.17134 x86_64)
at Object.checkLegacyResponse (C:\Users\khyati.sehgal\source\Workspaces\QA\SAND-DEV-1\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:546:15)
at parseHttpResponse (C:\Users\khyati.sehgal\source\Workspaces\QA\SAND-DEV-1\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:509:13)
at doSend.then.response (C:\Users\khyati.sehgal\source\Workspaces\QA\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:441:30)
at

Continue reading “protractor- session not created: Chrome version must be between 70 and 73”

Agile Testing, Automation, Automation Framework, best practises, protractor, Scrum, Selenium, Web Automation, Web Testing

Getting started with the protractor

As an automation QA Engineer,  I always try to work on areas where I can work with pace and efficiency, technology doesn’t matter. As the world is moving towards scripting language We as a QA also work together.

I am talking about the AngularJS, ReactJS applications which are highly acceptable and readily used in today’s world be it a Banking app or a CRM based. One can connect to all the application with frontend as a JS app and backend can be anything C# , Java ,etc. Here the role of QA is to identify the best fit he/she can apply to quickly automate all the cases in a highly compatible language which supports the Frontend application.

Here, I am talking about protractor. For one of my applications which is written in Aurelia (FE tool to create an application similar to AngularJS) we decided to work upon protractor, let’s talk about it in this blog how we managed to do it.

When it comes to testing applications, there are two main types of tests one wants to cover: Unit and E2E . End to end usually refers to the QA testing and unit mainly for the developers to take ownership of.

Continue reading “Getting started with the protractor”

Agile Testing, Loggers, Selenium, Selenium Errors, Selenium Webdriver, Uncategorized, Web Automation, Web Testing

Setting loggers in Selenium

Imports to make

import java.io.File;
import java.io.IOException;
import org.apache.log4j.ConsoleAppender;
import org.apache.log4j.Level;
import org.apache.log4j.LogManager;
import org.apache.log4j.Logger;
import org.apache.log4j.PatternLayout;
import org.apache.log4j.RollingFileAppender;

Continue reading “Setting loggers in Selenium”

Agile Testing, Automation, central repository, collabration, git, Maven, version control

Basic commands to start working with git.

In one of my previous blog, I have shared my experience why we need to use ‘Git’. In this post I will share basic commands to start with.

So lets get started.

To start with you need a machine where you want to use git. The choice would be of Windows, iOs, Linux, etc. The links would be same for different operating system, you just need to choose the one best fits your computer system.

Continue reading “Basic commands to start working with git.”

Agile Testing, central repository, collabration, Continuous Integration, git

A quick beginners guide of git.

The team is when more than 2 people work on a small goal to achieve some concrete task. On every single day we get daily tasks to complete with timelines. From getting up for office, to reach home back, from preparing food, to have lunch on time, from reaching the office on time , having dinner with family on time. Hand-in-hand, we have similar official tasks which are prominent and can cause problem if not met. So as a person all we need is tracking of time, things, tasks and at the same time sharing the same work done or work in progress with each and every member be it a family member or team member.

Continue reading “A quick beginners guide of git.”

adb, Agile Testing, android, Automation, Functional Testing, Java, Mobile Testing

ADB for mobile quality analysts.

As we (QA) are growing more towards automation, we have now started exploring tools which developers are using for their development. Not just for developing our own testing framework but also for capturing logs, checking code smells, etc we can use adb.

And I think this is very cool and good to start exploring in this direction, as learning is never ending and shall never stop. Mobile testing is very dynamic and in this blog I will share some experience over adb for android testing and debugging.
Continue reading “ADB for mobile quality analysts.”

adb, Agile Testing, android, Automation, Mobile Testing, MTP, PTP

How to start mobile testing in android.

There are multiple approaches you can take to kick start mobile testing. For this you need to understand what you are actually trying to achieve and what constraints you have like how many team members, testing devices, etc.

The first thing you have to have a good environment to start with. There are two ways to do the same one via emulators, and the other on actual devices. Emulators are easily available, free of cost though they are very slow and real results are hard to capture in them. While real devices are fast which lead to real results and are easy to use. 
Continue reading “How to start mobile testing in android.”

Agile Testing, Automation, best practises, central repository, collabration, Functional Tests, git, Java, Manual Testing, Maven, Test Cases, Testing, version control, Web Testing

Making code commit in a better way.

Developers always work for their growth and betterment be it a niche technology or any fast technique.
Here in this post I have listed some points which if kept in mind before committing code in central repository(like git) can help an agile team in saving time and achieving improved quality of work.
 better-code

Continue reading “Making code commit in a better way.”

Agile Testing, Automation, Automation Framework, best practises, Java, Java Class, Java Object, Object Oriented, Selenium, Testing, Web Automation, Web Testing

Part 2 – Resolution of some major-frequently-seen Selenium utilities.

This blog is a continuation of my previous blog . Here I am collating the data according to my own experience. These methods can be added in the Utility class directly to make wide use of different functionalities.

Continue reading “Part 2 – Resolution of some major-frequently-seen Selenium utilities.”

Agile Testing, API testing, Automation, Automation Framework, HTTP, HTTP methods, rest assured, Selenium, Selenium grid, Web Automation, Web Services, Web Testing

Part 2-API testing with rest assured.

In continuation with my previous blog, here I will be sharing some basic rest services methods implementation like POST, GET etc.

api

REST in itself without exception has a lot to learn. It has helped the whole team of developers and QA to evolve and mobilise their work as much as possible.

By providing whole lot of the methods like GET, POST, PUT, DELETE, PATCH, etc one can traverse the whole code. Not just fetching, or updating, one can even delete then store and use one data in one and another form. Thus making a complete round of testing and development done.

Like REST java also helped in making this dynamic thing more super, lets see how.

Continue reading “Part 2-API testing with rest assured.”

Agile Testing, Automation, Helium, Quality Analyst, Selenium, Testing, Web Automation, Web Testing

Helium .. a boon or not to all automation engineers?

‘Selenium’ is the hot-topic in the automation sector, if any developer or tester knows Selenium well, then it is considered  as he can do anything which is required to perform ‘Web automation’. Its been almost a decade when Selenium came up to the market, and as the time passed it became more and more popular. People started taking it more seriously. Not only as a stand-alone tool, merely with the combination of other tools like Maven, Jenkins, TestNG, etc.

Though the work goes on, and people started taking more interest in this automation area, people started finding flaws in this tool. However some were very genuine, on contrary some seems to make less sense.
Continue reading “Helium .. a boon or not to all automation engineers?”

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”