It’s been quite a while when the keywords DevOps and SecOps hit the world. It slowly became a trend and why does QA fall behind, right?

In the agile world, by all means, QAOps exist and guess what, it has been working like a charm in a lot of cross-functional teams.

QAOps has lead open a gate with a plethora of areas to test, learn, experiment, build and rearchitect the ways we used to test or even manage our test infrastructure.

So, what is QAOps?

QAOps in action comprises of but not limited to the following;

Testing at scale and Scale for testing:

These two may sound like synonyms but in fact, are two different paradigms and QAOps fits perfectly here.

(Dev + QA)* Ops = DevOps + QAOps

Yes, it is precisely that ways, there are no silos of Dev or QA or Ops. QA helps dev in both finding and fixing bugs, similarly, Dev helps QA in introducing new flavours in architecture and now the Ops part of it, wherein they both actively approach QA and dev with an operations angle.

Continuous development, continuous testing and hence continuous highly quality deliverables, using the best possible tools to facilitate this flow.

IAAC: Infra As A Code

Is no longer a concept for DevOps or devs, but scaling your test infra now needs detailed, precise and hence plan for gigantic architectures to scale for any kind of tests.

QAOps is also about going beyond cliche testing approaches and areas. It’s about digging deeper into deployments, performance, security, monitoring.

It ranges from about challenging Kubernetes cluster configs to monitoring milliseconds of changes in the performance, to also be able to pick an issue in what microservices to whitelist and what not if we had to deep dive into security aspects.

QAOps is also about testing the deliverables by DevOps.

Of course, QAOps includes automation, selective and precise automation which would deliver the most ROI.

Build, deploy and test is what we all are familiar with and is commonly termed as continuous integration in our humungous world of software products.

Each build has new code commits, fresh changes in UI/functionality and sometimes even legacy code gets altered to accommodate changes but we always execute same old regression tests with same old stale data. Isn’t it unfair?

Not arguing that regression is to be executed on same static data, but what if your test data is equally well framed to match your regression testing requirements but in each run, it is unique and has about 40% more chances of finding new bugs?

Eyes wide open?

Yes, you heard it. In my workplace we did an experiment which further led to the creation of “Continuous Test Data Generators” and today we execute about 1000+ test cases on fresh data and has helped find regression as well as bugs in new functionalities with very little or no changes in scripts or data drivers.

In this session, will be showcasing:

— How and why you need continuously generated fresh test data for your daily, nightly or even smoke tests. How to create such generators in few simple steps.

— How this test data helps find bugs and keep your test environment fresh and lively with new data and hence appears to be like production data which you never ever get to see in test environments.

CTDG is a conglomeration of automated test data generation as well as back-end data injection in order to achieve much more speed and accuracy.

The test data generated is goal-oriented and pathwise, so as no data is raw data, thus needing some amount of human intervention in terms of the application under test.

With the increased pace in adoption of agile methodology, testing is now becoming really complex in relation to the not so simple yet sweet demand of every project manager: "Why don’t you automate test cases while you test?"

Having worked and counselled in product giants and more than 5 startups in India, we would like to throw some light on what fits the test automation use case. Is UI automation "the Only way to test efficiently?"

The main issue with startups following Agile is “time crunch.” With multiple deploys a day and a fast paced development cycle, how does one find time to automate the product?

In this session, we will be sharing some methods/tools/techniques which increase the overall test coverage and have worked well in the past for startup culture.

A demo of some simple, useful and robust tools used for API, UI and Performance testing will also be given.

Push Notifications are the latest way of sending updates to our users. More and more Organisations are implementing Web Push Notifications along with emails and other notification systems.

So the Big Question that arises is "How do we automate them?"

We have come up with a library in various languages which can be integrated with your Automation suite and provide you everything you need about the notification triggered.

You can easily then trigger and verify the push notification sent and ship out the product without worries :)