Using a Combination of Scripted, Automated and Exploratory Testing for Optimum QA Coverage

Most test teams today are struggling to find better ways to handle their testing. With the advent of Agile in our software development processes, teams are perennially under pressure to provide faster releases without lowering their standards of quality. This, in turn, adds load on the in-house test teams to ensure finding more and crucial issues and to prevent defect leakage. For this reason, testers look at strategies and practices that can help them achieve their goals and add more value to the product’s quality.

In my opinion as a hands-on agile tester, there is no single silver bullet to quality, but a combination of different types and approaches to testing that can help us get closer to our quality goals. Test teams need to strategize and plan the usage of a combination of scripted tests, automated tests as well as exploratory tests for achieving an optimum coverage and best quality software.

Here is my latest article for PractiTest QA Learning Centre where I discuss the need to have a combination of scripted, automated as well as exploratory tests for an optimum QA coverage–

https://www.practitest.com/qa-learningcenter/thank-you/exploratory-testing-optimum-qa-coverage/ 

Scripted Tests

When we look at the typical test approach, it begins with test scripting and designing tests as per software functionality. These are created using requirement analysis and test design techniques and also using common sense and skills by our skilled testers. These scripted tests form the starting point of testing a new feature, change or addition in the software.

Automated Testing

In addition to running the scripted tests manually, testers also rely on automated tests. These tests are scripted using various test automation tools and test automation, i.e. ability to write these automated test scripts is, thus, a much-wanted skill nowadays for all test professionals. The ability to run some tests using automated scripts helps repeatability and saves a lot of time and effort on part of the test teams. But most importantly, by automating the drudgery away, it saves the tester from repeated manual laborious tests and frees up their time for more creative thinking and exploration around the application.

Exploratory Testing

Exploration of software is basically looking at the feature/functionality/change and overall behavior from a learning as well as a critical standpoint. Exploratory Testing is a crucial aspect of software testing, which almost every tester performs knowingly or subconsciously.

Cem Kaner coined the term Exploratory Testing in his book “Testing Computer Software” and described it as:

“Simultaneous test design, test execution and learning with an emphasis on learning”

https://www.practitest.com/qa-learningcenter/thank-you/exploratory-testing-optimum-qa-coverage/ 

Read More »

Pic Credits blog.commlabindia.com

Factors To Consider When Selecting The Right Software For Your Business

Running a business in today’s tough competitive world is not everyone’s cup of tea. You need to be well ahead of your competitors in terms of marketing, services as well as technology. Being a business owner, you should always look up for software tailored for your business, which can simplify things for you, your customers or even your employees for that matter. Not only this, you should try to extract the best of possible from that software.

Many business owners are unaware of the advantages of having the right tools at hand. And those who realize it may lack the knowledge on choosing the correct software for their business. So here is a guide to such business owners about what factors they should keep in mind while choosing the right software for their business.

  • ANALYSE YOUR NEEDS

You should be clear in your mind about your needs. There are two kinds of software, one that is general to all kinds of business. For example, general accounting, and the other one which is specific to a particular kind of business. For example, a restaurant owner would need software which can manage recipe cost along with the front-of-house to back-of-house communication, or a manufacturing business may need a software which can track shipments and provide supply chain information.

  • THE COST INVOLVED

Cost is a really crucial factor in choosing a software. You have to see to it that whether you can reasonably afford to purchase new software for your business or not. And if it is a sure thing, then you should take into considerations the features that you will need both now and in the coming few years. You should not be willing to pay for bells and whistles or functions that are not required in your business. Before choosing a software, carefully analyse your needs and keep in mind not to alter your needs to fit the software.

Read More »

Crafting User Stories That Agile Teams Will Love

A popular term you will come across when working in agile is the “user story.” For the uninitiated, a user story is a technique of expressing software requirements in a specific format, usually:

As a < role of user >, I want to < perform an action >, so that < goal of user >

This adds more detail and description, and it’s sure to include the real need of the user when expressing the requirements.

For agile teams, user stories are a typical way to begin a conversation about a feature. But issues arise when we stop adding more beyond the one-line user story format. Most agile teams are crippled by incomplete, ambiguous and vague user stories that lack depth and details.

In my experience, there are some ways we can ensure that the user stories we craft are usable and valuable in all aspects. In my latest article for Gurock TestRail Blog, I talk about strategies to craft meaningful, understandable and valuable user stories for your agile teams.

We discuss INVEST Principle of User Stories, 3Cs of a User Story and how to learn from Experience of past sprints to improve your user stories. Read the full article here-

https://blog.gurock.com/crafting-user-stories-agile-teams/ 

Cheers

Nishi

5 Mistakes to avoid in Agile Retrospectives

Retrospectives are an integral part of every project we undertake, as well as a key ceremony in the Scrum lifecycle. Agile principally stresses the need to perform periodic meetings to reflect on the functioning of the team, their processes and actions and try to improve their shortcomings, so retrospectives are essential. The team gets to look back on their work and answer three key questions: What went well? What did not go well? How can we improve?

Even if agile teams perform retrospectives as a regular part of their project lifecycle, there are a few common mistakes they may be making due to a lack of understanding, perspective or communication, and these mistakes can prevent obtaining the maximum benefits of the retrospective.

In my article for Gurock TestRail blog, I have discussed five common mistakes that we must avoid in Agile Retrospectives.

 

Click Here to Read more

Do let me know your thoughts!

Cheers

Nishi

 

Key QA and testing takeaways from the Agile manifesto

My first article for Global App Testing blog is now published at

https://www.globalapptesting.com/blog/key-qa-and-testing-takeaways-from-the-agile-manifesto

             >>>Agile testing leaves very little time for documentation. It relies on quick and innovative test case design rather than elaborate test case documents with detailed steps or results. This mirrors the values of Exploratory Testing. When executed right, it needs only lightweight planning with the focus on fluidity without comprehensive documentation or test cases. 

From a QA viewpoint, we can learn from the Agile Manifesto key goals; communication, efficiency, collaboration and flexibility. If you improve your QA team in these areas, it will have a positive effect on your QA strategy and company growth.

>>>The Manifesto for Agile Software Development forms the golden rules for all Agile teams today. It gives us four basic values, which assure Agilists a clearer mindset and success in their Agile testing.

Although these values are mostly associated with Agile development, they equally apply to all phases, roles and people within the Agile framework, including Agile testing. As we know, Agile testers’ lives are different, challenging and quite busy. They have a lot to achieve and contribute within the short Agile sprints or iterations, and are frequently faced with dilemmas about what to do and how to prioritise, add value and contribute more to the team.

The frequent nature of development in Agile teams means the testing methods used need to respond to change quickly and easily. In that way, Agile testing shares some important characteristics with exploratory testing.

In this article I examine the four values of the Agile manifesto to find the answers to an Agile tester’s dilemmas and improve their testing efforts. Read More

Please give it a read and share your thoughts!

Happy Testing!

Nishi

 

A simplified Agile Test Strategy for Cross Environment Testing

Cross environment testing is viewed as a tedious and repetitive task and is generally a challenge to accommodate within an agile life cycle. In my recent guest post for Gurock, I showcased my own experience in an agile release wherein we created a strategy for coverage of a number of test environments to support.

Using simple steps, discussions, base-lining and agreement within the scrum team, we created a scalable interoperability test strategy which was later supplemented with automation and other tools. In this article I have talked about-

  • Testing across OS versions
  • Supporting System versions
  • Localization- multiple language support
  • Planning and Test Strategy creation
  • Additional Ownership by testers

To read more, click here.

Give it a read and share your thoughts-

https://blog.gurock.com/agile-cross-environment-testing/

Print

Thanks

Nishi

Five Ways DevOps complements Agile

My guest post article for Gurock Software GmbH #TestRail blog is now up!!

“5 Ways DevOps complements Agile” – As an industry practitioner who has worked in agile for almost a decade now, I have always seen DevOps as a friend and an extension of agile. Using this article I have tried to put across my view on how this handshake between developers and operations personnel works in favor of bridging the gap from software creation to software delivery.- 

Please give it a read at – https://blog.gurock.com/5-ways-devops-complements-agile/

The major points I have touched upon in this article are –devops

  • A Focus on User’s Needs

  • Continuous Delivery

  • Concentrated Value Creation

  • Motivated Individuals

  • A Culture of Inclusion

 

To read more click here->

Cheers

Nishi

 

Getting Featured in the ‘Top 10 Articles of 2017’ at Stickyminds!

Dear Readers

It is my pleasure and honor to share that my article on

                              “Let the Agile Manifesto guide your Software Testing”

published on Techwell Community forum http://www.stickyminds.com in 2017 has now been featured in the list of “Hottest Articles of 2017” , featuring in the Top 10 Most Read articles last year!

You can give it a read at https://www.stickyminds.com/article/let-agile-manifesto-guide-your-software-testing

I am happy that my thoughts, ideas and write-ups are getting noticed, and this motivates me to continue writing more and better always!

Wishing you a great year ahead.

Happy Testing!

 

Agile Testing Reflections 2017

My first guest post article for Gurock Software GmbH is now up!!

“Agile Testing Reflections 2017” – I have written this as a look back on 2017 – what we learnt this year and taking these learnings forward to the new year.

Please visit https://blog.gurock.com/agile-testing-reflections-2017/  and give it a read.

The major points I have touched upon in this article are –

         Users are and Always will be King

         DevOps is our Friend

         Skills are More Important than Tools

         ‘Contributor’ vs ‘Tester’

Read the article here –>

Thanks

Nishi