Prevention is the Best Cure- for Defects in Agile

The agile methodology focuses on building in quality from the very beginning of the software lifecycle. That is why we aim to find and fix defects early on: A defect found and fixed in an earlier lifecycle phase is a multitude cheaper than the same defect at a later stage.

But how can we more easily make it possible to prevent defects from percolating deeper in the software development lifecycle by fixing them in their nascent stages?

This is the main theme of my latest article for @Gurock TestRail blog – where I explore and explain ways to foresee, analyze and thwart defects in an agile context.

The main points discussed are-

Communication

Conduct Reviews

Demonstrate Often

Static Analysis and CI

Click Here to read the complete article –>

Please support by liking / commenting and sharing the article!

Cheers

Nishi

My experience speaking at Selenium Day

I was invited to speak at the Selenium Day event in Bangalore on 31st Jan 2019.

I presented a 1 hour workshop about Selenium-Cucumber Integration and showcased it with a short demo. The session was received well and greatly appreciated by the audience.

The day was filled with lots of engaging conversations and learning from other speakers and sessions.

Here is a glimpse into the event-

I am speaking at ‘Selenium Day’- 31st Jan @Bangalore

I am glad to announce that I will be speaking at the upcoming event

“Selenium Day” Event being organised by 1.21Gws on 31 Jan 2019 @Bangalore

I will be taking a 1 hour workshop on

“Selenium Integration with Cucumber for an extended BDD framework”

This workshop will cover
• Practical issues faced by most testing teams
• Behavior Driven Development – the definition and need
• Extending the Agile User stories and acceptance criteria in BDD scenarios
• Cucumber as a BDD tool
• Integration of Cucumber with Selenium in order to perform functional tests
• Demo using Cucumber with Selenium with a real use case
• Usage and Benefits of BDD In agile teams

For program details and complete agenda of the event, visit the website

https://1point21gws.com/selenium/bangalore/

The event will have enthusiasts exchanging ideas on advancing the present and future of Selenium and will bring together bright minds to give insightful talks pertaining to Selenium practice that are solution-focused, and foster learning and inspiration.
* Solutions for Practical issues of testing.
* Integration of Selenium with other testing tools.
* Providing a key meeting place for Selenium Professionals and Executives from leading IT organizations.
* A platform to share your research and experience 

Looking forward to sharing my experience, learning from skilled professionals in the area and networking with the brightest minds at the event!

-Nishi

Look Back to Plan Forward – Learnings from 2018

Every year we see the software industry evolving at a rapid pace. This implies changes in the way testing is conducted within the software lifecycle, test processes, techniques and tools, and the tester’s skill set, too.

I’ve been into agile for more than a decade, and I’m still learning, changing and growing each year along with our industry. Here are five of my key lessons and observations from 2018. I hope they help you in the coming year!

https://blog.gurock.com/lessons-for-agile-testers/

In my article published on Gurock blog, I talk about the 5 key learnings for Agile testers from the past year and how they will be key in planning your road ahead in 2019. The key learning areas discussed are —

Testing Earlier in DevOps

Getting Outside the Box

Increasing Focus on Usability Testing

Enhancing Mobile and Performance Testing

Integrating Tools and Analyzing Metrics

Click Here to read the complete article — >

‘Just Enough’ documentation in an Agile Project

Agile poses many challenges to the development team, most of them pertaining to time. Teams are perpetually under pressure to deliver working software at a fast pace, leaving minimum time for anything else. When testing on an agile project, learning how to write lean documentation can save precious time. Furthermore writing lean documentation can help rework efforts by focusing only on what’s really necessary.

The Agile Manifesto emphasizes working software over comprehensive documentation, but most agile teams interpret this wrong and treat documentation as something to be avoided, owing to time constraints. The manifesto states a lesser focus on comprehensive documentation, but some documentation is still needed for the project and any related guidelines being followed. Attaining this balance is a challenge.

Documentation is a necessary evil. We may think of it as cumbersome and time-consuming, but the project cannot survive without it. For this reason, we need to find ways to do just enough documentation — no more, no less.

Read about how to focus on important areas like VALUE  , COMMUNICATION and  SUFFICIENCY when documenting in your agile project – in my article published at Gurock TestRail blog –> https://blog.gurock.com/lean-documentation-agile-project/

just enough

Click here to read the full article

For example, in a traditional test design document, we create columns for test case description, test steps, test data, expected results and actual results, along with preconditions and post-conditions for each test case. There may be a very detailed description of test steps, and varying test data may also be repeatedly documented. While this is needed in many contexts, agile testers may not have the time or the need to specify their tests in this much detail.

As an agile tester, I have worked on teams following a much leaner approach to sprint-level tests. We document the tests as high-level scenarios, with a one line description of the test and a column for details like any specific test data or the expected outcome. When executing these tests, the tester may add relevant information for future regression cycles, as well as document test results and any defects.

More examples and scenarios for learning leaner test document creation are included in the full article– Click here to read the full article

 

                 Are you interested in finding the right tool for your Agile processes? Here is a comprehensive assessment and comparison of the best agile tools available! 

https://thedigitalprojectmanager.com/agile-tools/

Prepared by Ben Aston, this list may be a useful guide for finding and selecting the best tool to support your agile journey. Check it out!

 

Happy Testing!

Nishi

The 12 Agile Principles: What We Hear vs. What They Actually Mean

The Agile Manifesto gives us 12 principles to abide by in order to implement agility in our processes. These principles are the golden rules to refer to when we’re looking for the right agile mindset. But are we getting the right meaning out of them?

In my latest article for Gurock TestRail blog, I examine what we mistakenly hear when we’re told the 12 principles, what pain points the agile team face due to these misunderstandings, and what each principle truly means.

 

Principle 1: Our Highest Priority is to Satisfy the Customer Through Early and Continuous Delivery of Valuable Software

What we hear: Let’s have frequent releases to show the customer our agility, and if they don’t like the product, we can redo it.

The team’s pain points: Planning frequent releases that aren’t thought out well increases repetitive testing, reduces quality and gives more chances for defect leakage.

What it really means: Agile requires us to focus on quick and continuous delivery of useful software to customers in order to accelerate their time to market.

Principle 2:

Check out the complete post here —- Click Here to Read more–>

 

Do share your stories and understanding of the 12 Agile Principles!

Cheers

Nishi

My interview with Thomas Cagley featured on SPaMCAST

I recently had a chance to chat with Mr. Thomas Cagley in an interview for his wonderful Podcast channel SPaMCAST. We talked all about Agile Testing, its differences from the traditional approach of testing, Agile Pods and the upcoming trends in the testing world!

It was a wonderful experience and I am grateful for having the chance to talk to one of the people I so look up to in the industry. Here is the link to the podcast show notes and info

http://spamcast.libsyn.com/spamcast-516-agile-testing-and-more-an-interview-with-nishi-grover-garg

Here is the link for Direct Playback: bit.ly/2QKvPvm

 

Hear it out and do share your thoughts!

Cheers

Nishi

 

Optimize Your Hardening Sprint for a Quality Advantage

A hardening sprint is an additional sprint that some teams run to stabilize the code and ensure that everything is ready just before release. Agile teams vary in their opinions on using hardening sprints in Scrum, but if your team does agree on having one before your release, there may be a lot to be done and varied expectations from the product owner, testers and developers. It may also lead to other work being delayed, leading to accumulation of technical debt.

In my article for Gurock TestRail Blog, I have discussed some tips on optimising the hardening sprint and achieving the maximum quality before release.

I talk in detail about some main points to focus on–

  • Plan Ahead
  • Perform End-to-End Testing
  • Perform Non-Functional Testing
  • Perform Tests on Other Platforms and Languages
  • Reduce Lower Priority Defect Counts
  • Use your sprint Wisely

Read the full article here — > https://blog.gurock.com/optimize-hardening-sprint/

Please share your thoughts!

Happy Testing!

Nishi

A Day in the Life of an Agile Tester

An agile tester’s work life is intriguing, busy and challenging. A typical day is filled with varied activities like design discussions, test planning, strategizing for upcoming sprints, collaborating with developers on current user stories, peer reviews for teammates, test execution, working with business analysts for requirement analysis and planning automation strategies.

In my article for Gurock TestRail blog, I have explored a typical day in the life of an agile tester and how varied activities and tasks keep her engaged, busy and on her toes all the time!

agile tester.png

Let’s sneak a peek into a day in the life of an agile tester — > You will go through the daily routine of an agile tester and will experience their complicated schedule in real time.

Read full article

https://blog.gurock.com/agile-tester-work-life/

 

ATA Bangalore 19th Meetup hosted @Coviam – Event Round Up

I, representing Agile Testing Alliance, organised and hosted the 19th ATA meetup @Bangalore on 28th July 2018 in association with CovaimTech . The event was themed as “The Future of Testing” and was aimed at bringing awareness on new trends in the world on agile, testing and devops.

Mr. Manoj Kumar Vijayaragavan (VP of QA Engineering, Coviam) gave an introductory talk about QA practices and technologies used at Coviam. We had speakers from Coviam present enlightening talks on topics like “Deployments at Scale” by Ankit Tripathi (DevOps Engineer) and “Integrating Microservices for continuous testing” by Viswanatha Reddy (Senior SDET, Coviam) , which were highly appreciated.

We also introduced for the first time in this meetup, the concept of Lightening talks, wherein we opened registrations for any interested delegate to take the stage and present any idea for a short 10-minute duration. This idea got two speakers Mr. SarathKumar M.V. presenting on Microsoft Azure testing capabilities and Mr. Rakesh Reddy talk about “Accessibility Testing Strategy”. The short and crisp talks brought out valuable discussions and garnered interest from the audience.

Our gracious hosts @Coviam had arranged for tea and we had a brief networking break.

Our third speaker was Ms. Bhavani Sruti from Moolya who presented a hands on session on Mobile App Performance Testing, wherein we engaged the audience in performing some tests on their own mobiles first-hand and explaining the various performance parameters for mobile apps.

The last segment of the meetup was the Agile Games. I along with Mr. Nagesh Deshpande from Cynosure had planned some quiz questions, and Pictionary words to play amongst the delegates divided into teams. The audience had the chance to win ATA goodies, and the teams were awarded with goodie bags! The delegates had loads of fun playing the games and thus the event ended on a high note!

Thus ending the event, we took part in lunch arranged, and discussing various other interesting ATA events coming up soon.

Here are a few glimpses of the event-

Talks-MeetupCoviamGames-MeetupCoviamFelicitations-MeetupCoviam

Looking forward to organising many more such events to encourage and bring together the testing community!

Cheers

Nishi