How to Decide if You Should Automate a Test Case

Test automation is imperative for the fast-paced agile projects of today. Testers need to continuously plan, design and execute automated tests to ensure the quality of the software. But the most important task is to decide what to automate first.

In my article published on the TestRail Quality Hub, I have compiled & shared a list of questions to help you prioritise what you should automate next and guide your test automation strategy.

Here is a checklist of questions to ask yourself as you decide on automating a Test Case–

*******

Is the test going to be repeated?

Is it a high-priority feature? 

Do you need to run the test with multiple datasets or paths? 

Is it a Regression or Smoke Test?

Does this automation lie within the feasibility of your chosen test automation tool?

Is the area of your app that this is testing prone to change?

Is it a Random Negative Test?

Can these tests be executed in parallel, or only in sequential order?

Are you doing it only for the reports?

********

For the detailed explanation of each of these points, read the complete article here –>

Are your Test cases really effective?

Test teams are forever designing and adding new tests, running them, and reporting results. But is your test team creating tests that are effective at finding real problems?

How do you know if your tests are actually working, and not just adding to the ever-increasing test count?

In my article published on the Testrail blog site, I discuss some ways you can gauge the effectiveness of your tests — and improve them.

Defects Found

The top and most obvious indicator of the effectiveness of your test cases is the defects you find when executing them. As you and your team execute the designed test cases, constantly ask yourself these questions:

  • Are these tests guiding me toward defects?
  • Am I finding problems with the predefined test cases? Or do I have to do more exploration before even getting close to a problem?
  • Are these tests exercising unique flows or use paths?

Metrics

You can also look at your defect lists and find related test cases for the defect logged (if you have that ability in your defect management system). This interlinking helps the team understand what test cases led to the issues found.

You can then further analyze whether that test case was created during test design or later added to the list when the issue was found.

Exploration

If your test cases are not effective, you will not find any useful bugs in test execution. That will mean most of your time is spent in unplanned exploration or ad hoc testing. So, by looking at the time spent in actual test execution versus the time spent on ad hoc testing, you can figure out the effectiveness of the test cases you designed.

If your test cases are effective, you will find issues, explore more use paths, navigate through different integrations with other features, and test different aspects of the same functionality.

If at the end of your test execution, you feel that you have not done all of that, you can infer that is because your test cases might be too simplistic or obvious, and therefore not effective enough to find any useful bugs.

History

Continue Reading here–>

My interview with Fabian Böck featured on Youtube -“Never Feel Stuck”

I was recently invited by Fabian Böck for a chat over on his Youtube channel where he frequently interviews people in tech on various topics of interest in the industry. My talk was focused on how to steer the direction of your tech career. We had a fantastic talk about how to pave learning avenues, set for yourself time to reflect, and how companies should be enabling their workforce. And most importantly, how to ‘Never Feel Stuck’ in where you are – even if you are happy or not and use continuous learning and self improvement to guide yourself to better places!

Here is a link to the video interview-

Fabian’s company Boeck and XOXO works on Tech Conventions x Matchmaking Marketplace x Tech Talks. Check them out for more interesting talks and content!

Check out the Linkedin posts here – https://www.linkedin.com/feed/update/urn:li:activity:6821385665146691584/

Cheers

Nishi

3 Ways Technical Debt Can Actually Help Improve your Sprints

“Debt” is not a pleasant term. It brings to mind a burden and generates a feeling of anxiety. The same may also be true for technical debt, or the extra work that we incur while developing our software in the form of missed quality targets, pending tasks, or skipped points from our exit criteria checklists. Like monetary debt, technical debt happens when we make a decision that is quicker in the short term but will hurt us in the long term.

Though we may try our best to limit this debt, it will still happen. And while we will need to pay back the debt one day, we can also use it as a lesson to help improve ourselves and our processes. If it ultimately helps our development, it doesn’t even always have to be a bad thing.

In my article published on the Ranorex blog site, I examine three ways technical debt can actually help us improve our sprints.

Better Estimation

Though the first time incurring technical debt due to an inability to complete an activity as planned may not be pleasant, it should consequently improve the team’s estimation and planning.

Let’s say we had defined developers’ tasks for all user stories with estimated hours, along with a mandate of peer reviews being performed for all code being written. But the end of the sprint saw that though the developers marked their development tasks as done, none of the code had been peer reviewed before check-in. It could have happened due to lack of time or ownership.

The next sprint, the team then decides to have a separate sub-task for peer reviews under the development tasks, each of which is assigned to a peer with an allotted time of 30 minutes. This helps the team plan, have clarity around what tasks are pending, and see how much effort is being spent on the tasks.

So, even though you may begin to accumulate technical debt early on in your sprints, understanding the cause and having a plan of action may improve the team’s overall performance.

Sequencing and Prioritizing

If you find yourself at a point where release is a couple of sprints away and you have a number of unresolved defects, even though they are lower severity, the team may decide to reduce open defect counts for a sprint rather than adding new features. The technical debt incurred in the form of defects can urge the team to refocus and shift priorities.

Or, let’s say your team agreed to 70% automation of regression testing in the beginning of the release cycle, but after four sprints, the scripts they created are showing signs of being unmaintainable or not scalable enough. This may affect delivery in the end, so some testers may take the call of focusing full time on reworking the scripts and adding new automated tests to them, while the other testers take up functional and regression tasks.

My team once found out at the end of our fifth sprint that our developers had not been performing static analysis of their code or creating the reports that were mandated for every sprint. Whatever may have been the reason, this meant that running those reports now was leading to hundreds of errors or warnings all pertaining to code formatting, naming conventions and comments. Even though these were minor issues, it required time to get them all corrected with thousands of lines of code.

Read More »

Achieving the Goal of In-Sprint Test Automation

Getting test automation done is a challenge, especially within the tight deadlines imposed by Scrum. As much as the thought of continuous in-sprint test automation sounds enticing, the practicality of it may elude most Scrum teams.

In my article published here– I look at some of the main things you need to consider in order to get your test automation done within the confines of your sprint.

Framework

The first thing to focus on is a framework that is useful, is easy to understand, and helps all stakeholders participate in test automation.

This is essential because you want to make test automation a continuous activity that is a part of daily work, not a once-a-sprint (or once-a-release) work item. For this to happen, the framework must make it equally comfortable for a businessperson, developer, functional tester or automation expert to add their contribution and see the results of their efforts.

There are many business-friendly frameworks and techniques, like behavior-driven development (BDD), as well as many tools that can create tests in a domain language and then translate them to script code.

All stakeholders must be trained on using the framework, and their area of contribution must be made clear to them, with practical hand-holding. The automation tester can then focus on maintaining the framework, generating test suites and editing failing scripts, while the creation of test automation will be a continuous task assigned to everyone involved.

Collaboration

The next thing to focus on is collaboration between the various stakeholders. A continuous automation framework can only survive when it is being fed and tended to by everyone on the team.

  • The business people, like a business analyst or a product owner, can help by adding user scenarios or defining the requirements in a framework-friendly format. This may require them to be trained on the preferred format based on the framework being used
  • The developers can help by creating reusable methods for steps of the script. They can also create and maintain an object repository for all elements they add to the UI while testers use the pseudo names of the elements in the test scripts. This means that the scripts can be created before (and independent of) the application UI, and such scripts won’t need editing when the UI changes, as long as the object repository is kept up to date
  • The testers can help by adding more scenarios, specifying and creating test data, and executing the scripts periodically

Strategy

How to strategize the development of test scripts is crucial to making in-sprint automation a reality. Using API-level automation whenever possible will reduce the time and effort.

Continue Reading –>

Read More »

10 Lessons When Moving from Waterfall to Agile

Many organizations take up the transition from waterfall to agile with the best intentions in mind. Like so many other companies, you might also be seeking to replace your traditional waterfall processes with agile in a quest to shorten the time-to-market and deliver high quality applications.

The road to agile, though, can be a rocky one! That’s why, in my latest refresh post for Ranorex blog, I have put together a few lessons and tips that will help you in succeeding in moving from waterfall to agile successfully!

The article was published at https://www.ranorex.com/blog/10-lessons-when-moving-from-waterfall-to-agile/

Here is a quick list of lessons we dive into-

1: Embrace the agile culture first

2: Adapt roles and responsibilities

3: Take a whole-team approach

4: Test early and often

5: Remember that agile is iterative

6: Encourage transparent communication

7: Make test automation your friend

8: Commit to early feedback and re-planning

9: Include the whole organization in the agile transformation

10: Adopt tools to enable team collaboration

Check out the complete article to read in detail about each of these learnings that can help you succeed in your agile transformation.

Cheers

Nishi

Taking a MasterClass with the Ministry of Testing!

I was invited to take a MasterClass by the wonderful people at the Ministry of Testing last month. They had a ‘Communities’ theme going on for the month of June 2021 and they loved my talk idea about Leveraging Tech Communities. So we worked around that theme to create a talk on “Grow your Career with Tech Communities”

I had an awesome time taking the #DojoMasterclass with Ministry of Testing . What a wonderful experience!

My talk focused on discussing-

  • How to leverage the power of communities in your personal and professional growth
  • How to contribute, volunteer and participate in communities
  • How user communities help in taking your company’s brand forward
  • How can companies create powerful and engaged user communities

I am grateful for the opportunity I got, the great feedback I received from the participants, and an awesome host Vernon Richards.

Thanks, Áine McGovernHeather Reid, and Simon Tomes for arranging the session! 🙂

Check out the recording on the Pro Dojo https://lnkd.in/gy24FvW

How to Access the recording

  1. Click on this Link  
  2. If you have a PRO Account, click on the GREEN Button on top of the screen “Sign In to View this Content” and sign in with your PRO Acount
  3. If you do not have a PRO Account, click on ‘Go Pro to view this content’ Register for the Pro Account
  4. You can now Play the recording!

6 Ways to Grow Your Testing Career in 2021

Last year was hard in more ways than one. Amidst the pandemic, lockdowns, and changing global political climate, we are still forced into a survival mode of sorts. While many people struggle to hold on to their jobs, others are having a hard time adjusting to working from home while managing kids, home life and distractions. As we are cooped up with all the chaos around us, our career and growth plans might have taken a back seat for a while there.

We are now pacing through 2021. As we pass the half year mark in 2021, let’s take back charge of our careers and drive them in the direction we want!

In my article published here earlier this year, I discuss six tips to get your career as a tester back on track, or even take it down some new paths!

Learn a new skill

Learning anything new, whether it’s a new language, a new recipe, or a life skill like swimming or cooking, can help open your mind and create excitement for learning other professional skills, too.

Learning a new skill has always been the first tip you get to advance your career, and that’s because it stands true now more than ever. It’s often necessary in order to upgrade yourself if you want to land a new job or a better role. But amidst all the chaos around us, our minds might not be the best focused on learning right now.

Whether you were impacted by the coronavirus pandemic and lost your job, or your plans for a job switch were impacted or delayed, do continue to spend time and effort on learning something new that you have always wanted to master.

Diversify your skills

Testing is a multi-faceted role, and testers need to possess multiple skills to be effective in their teams. Especially in the ever-changing landscape of DevOps and agile, being a tester requires skills ranging from test automation to API testing to functional testing to security, performance, and load testing. We also need to be familiar with build processes, automated deployment tools, and white box tests.

Still, whatever your current specialty, you can always acquire another skill to better your profile and expand your skillset. Here are some ideas:

diagram of skills for software testers
Mind map showing diverse skill sets a tester can acquire

Choose an area to specialize in

While it is important to know a little bit of everything, that might not satiate your hunger for knowledge! As you diversify your skillset, you are bound to recognize that you love a certain topic more, so you can then focus on specializing in that area.

As you dig deeper into that area of testing, you will learn more about the tools it requires, the best technologies to use, their comparisons, in-depth features, etc. This will help you participate more in discussions, showcase your advanced skill set, and eventually be seen as a go-to person for that job.

Continue Reading—->

<Image credits – https://unsplash.com/photos/wNz7_5EvUWU&gt;

How to Decide if You Should Automate a Test Case

Test automation is imperative for the fast-paced agile projects of today. Testers need to continuously plan, design and execute automated tests to ensure the quality of the software. But the most important task is to decide what to automate first. 

In my article published at the Gurock Blog website, I have have compiled a list of questions to help you prioritize what you should automate next and guide your test automation strategy.

Think of this like a checklist that helps you make automation decisions quickly and effectively and create a standard process around them for your team to follow. Here are the list of questions to ask yourself.

Do check out the complete article for a detailed discussion on each of these-

Is the test going to be repeated?

Is it a high-priority feature?

Do you need to run the test with multiple datasets or paths? 

Is it a Regression or Smoke Test?

Does this automation lie within the feasibility of your chosen test automation tool?

Is the area of your app that this is testing prone to change?

Is it a Random Negative Test?

Can these tests be executed in parallel, or only in sequential order?

Are you doing it only for the reports?

Test automation tools will provide you with useful insights into the quality of the software that you can showcase with the use of some insightful reports. But are these reports the only reason you are looking at automation? Just looking at the red or green status results of the test reports might not be the best way to assess the software quality. You will need to spend time analyzing the tests that failed, why they failed, and what needs to be corrected. Tests created once will need maintenance and continuous monitoring to keep them up to date. All of that needs to be kept in mind and the effort needs to be accounted for.

There is more to test automation than just the fancy reports!

Looking at the questions above, analyse the state of your test case, the intent behind its automation, and its feasibility, as well as the value that you might get out of it. Hope that helps you decide what tests you should or should not be picking for automation!

<Image credits – https://unsplash.com/photos/FlPc9_VocJ4 >

Read Along – ‘The Effortless Experience’- Chapter 8

“Effort Beyond the Contact Center”

Non-contact center applications of the Low Effort concept-

Customer Effort in Retail

Most critical factors when it comes to customer effort in retail environment are

“Navigability” – How easy it is for customers to find what they are looking for

“Issue Resolution” – How easy it is for customers to get help solving some problem.

Customer Effort in Product Design

Simplicity of design and ease of use really make certain products stand out in a crowd.

  • Apple’s ease of use is legendary.
  • Bose is another consumer electronics company that just ‘gets’ the idea of low effort. They put simple color-coded tags on wires that match the color of the jacks they plug into. Easy stuff!
  • TurboTax uses intuitive, plain-English, question based approach to helping taxpayers do their taxes.

Customer Effort in Purchase Experience

Decision Simplicity – Simplifying a consumer’s purchase decision

comes down to 3 things-

  • Making it easy for consumers to navigate information about the brand
  • Providing information that is noteworthy
  • Making it simple for consumers to weight their options

Effort should be reduced throughout the customer life-cycle.

Reducing effort in pre- and post-sales customer touch-points has measurable loyalty impact.

***

The Best companies Live low-effort.

Top brands are adopting the principle of a low-effort experience across multiple facets of their business, from product design to the sales experience.

***