Kristal Blog


Featured articles


Quality checks maintained at Kristal AI

Quality checks maintained at Kristal AI

Quality Assurance in software testing is nothing but a procedure to ensure the quality of the software products or services provided to the end-user by an organization.

A QA(Quality Assurance) process is a key element in product or service development.

QA process we follow during our release testing in three phases:-

1. New Feature Testing ->Test plan/Test cases Validation

In some feature development processes, it can be possible that we may miss some requirements or maybe some scenarios while referring to the confluence document.

New feature testing is a must when we add anything new to the software. An effective and attractive developed feature requires testing to be done to maintain the quality and the specifications of the features.

To start with new feature testing, we should have a clear understanding of the feature. Hence we focus more on planning and designing the test cases before we get the new features for testing. It helps us gather metrics of features and validate them.

Before releasing a new feature, it needs testing to determine the impact on users and applications. New feature testing aims to make sure software meets the business requirements.

By instant code changes or critical bug fixes that are made during releases, it can be possible that the team can forget to ensure that all the core functionalities of the software are working seamlessly or not and not breaking any other flows.

We make sure newly developed features has no bugs and work as per product requirements.

So we take care of :

  1. Verify initial smoke on builds in the first round of testing.
  2. Validate test cases /test plans approved by the business team.
  3. Sign off on feature testing by updating the status of Jira tickets and keeping track of the failures in a Google sheet.


-Help us to understand the business impact of the new feature and what improvements should be made before release.

-Helps in keeping a check on various integrations.

-It’s Useful to detect bugs before new features go live.

What we maintain:-

By reading the feature requirements or proposed solutions by stakeholders for any feature, sometimes the QA team is not able to understand the feature requirements properly.

To overcome the miscommunications between Business-Dev-QA teams,

In the confluence document Test Suites are maintained in confluence, tagged to the epic as well as the dev tasks, to give a holistic view to every stakeholder associated with the feature.

A test cases suite is a collection of test cases that have been written and drafted using the requirement specifications document. It allows QA to think and analyze which tests to run to manage the risks for software delivery.


-This ensures the tracking of test cases as well as timely reviews captured at a place.

-Helps to understand the feature requirements properly and is useful while testing the same.

-It helps to cover end to end feature testing.

We don’t get a clear cut idea about how a feature should work in the first iteration of the requirement phase. It may be possible to miss the edge cases while testing the feature requirements.

Every phase of testing has its methods and terminologies.

By using mind maps we create mind maps for most features and share them with the tech team to understand an overview of features. It helps us to understand complex flows as well as to cover the edge cases while testing.

Mind Maps not only highlight important facts but also shows the overall structure of features in software testing. It provides a creative way to logically plan the testing.


i) Mind maps provide a great overview of any feature, extremely helpful in planning and designing the tests.

ii) Collects all the information in one place.

iii) Very flexible and easy to maintain.

Sample Mind map:-

Adding the extra key attribute or changing something in the existing backend APIs could break the existing flow. Introducing a new API in the existing workable framework could introduce a bug in the existing feature.

We keep in mind and start testing live apps that are already on the play store and app store respectively for Android & iOS.

Backward compatibility tests are important because some users may operate the application on old Android & iOS devices.

We make sure nothing should break in the existing framework. So validating all the previous functionalities along with upgraded features. We maintain backward compatibility on every release.


- It is very useful to find the flow breakage at an early stage of the release.

- Effective for stability and manageability of the software applications.

- Ensure a good user experience.

Process of QA

While introducing the new business requirements it may be possible the feature could break or raise some issues/bugs for actual production users, few functionalities require the actual data to test the feature end to end adequately.

Migration testing includes testing with old data, new data or a combination of both, existing features and the new features.

For some features, we bring the data from production and perform feature functionality testing on actual user data. To check overall functionality flows is working or not with the actual user’s data.

Make sure the mapping at the field doesn’t change and verify that all data has been migrated accurately. Here we cover the maximum no of possible cases on migrated data. This testing plays an important role when data comes into the picture.


-Help to get clarity on how the feature will work for old and new users.

-It’s helpful to test the stability of the environment and ensure there are no connectivity issues.

-Help to perform testing throughout the entire data.

To get real feedback on an application and how the application is used.

Application Logs help to find the exact errors while testing, we can monitor the application. Verifying request-response between the server and the application. Testing client-server logs for all actions.

Validating User level reports on every release as a part of regression. Reports testing and DB Jobs validations can add true value to our SDLC. Job scheduling, logs and DB Jobs validation make the system healthy.


- It is Useful to solve issues quickly.

- Helps to track the application behaviour in the testing environment.

- Ensuring that the whole system passes testing.

Even though your website works perfectly on a desktop, it doesn’t mean it’ll render perfectly on mobile or tablets as well.

Our aim while doing the responsive design testing is to test whether users should see the same content with the same ease whether they are viewing the site on a desktop or a smartphone.

Nowadays, people mostly use mobile phones or tablets to view websites as it is easy to carry anywhere. Mobile responsive testing plays an important role to ensure that all the users get equivalent access to information on their devices.

With the help of BrowserStack, we do maintain the use cases to test at least the top three devices and different browsers.


- Helps to maintain the consistency of application regardless of device.

- Increases traffic toward the mobile application or tablets.

- Attract more customers that in turn increases user experience.

2. Existing Feature Testing ->Regression Testing

While introducing any new feature in an organization, a new feature may introduce bugs and compromise existing features.

Regression testing is a must which is primarily performed to ensure and verify that any code changes in the software do not cause any change in the existing functionality of the product.

We performed Regression testing to check the stability of all features.

Our team ensures that we maintain the updated regression test cases suite in every release and cover all possible functionalities in our platform.

It helps us to identify any functionality issues in an early stage of the release.


- Helps to improve the overall quality of the product along with ensuring a great user experience.

- Ensure software works as expected.

- Ensure effective testing results.

3. Overall Build Verification->Sanity Testing + Smoke Testing

Apps must be signed off on one last time before being elevated.

Before signing off along with regression for the release, we make sure the sanity and smoke testing on the builds are done. With the help of smoke testing, most of the defects are identified at the initial stages.

Sanity testing that we do in our organization is mainly to validate the functionality of the application and not detailed testing.

Smoke testing gives us an initial check that a new software builds and its functionality are stable.


- Smoke tests are used to test the initial workflow such as signup/login, KYC pages.

- Sanity tests ensure a run-through of the basic functionality of an application.


In Summary

As such, it’s important to make enough time for proper testing. Even with plenty of time allocated, you’ll probably need to prioritize certain tasks over others. By clarifying tasks and progress in this way, when things go wrong, it’s easy to understand what’s been done and how best to fix it.

As a QA tester, it can be easy to get frustrated with the flaws you find.

These can help you to better visualize your testing process.

We aim to make software bug free


Any software is not about defining and sending to production. It requires Quality and that is the main challenge for the QA team. Software testing is a fine whole process that ensures the perfect quality of the product. Finding out bugs can be a lot of fun, Real challenge is maintaining the bug-free software and ensuring that it meets the end-user requirements(thinking the way from the client). User Interface is the first thing that the user comes in contact with, good user interface attracts the UI testing also plays an important role in testing.

Ending on a positive note

Quality is the result of carefully put hard work from QA, it has to be part of the organization, not only the process.”


Priyanka Honale

April 26, 2022

Liked it?
Share it with your friends & colleagues!

Related articles

Go to Blog

Ready to start investing?

A fully digital onboarding process that can be completed within 15 minutes.
No more voluminous paperwork and queuing!

How would you want to invest?

Your Details

Financial Guide Details

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Your Details

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

I understand the financial products and would want to proceed with investing without a financial guide