Unveiling QA Processes in Software Development
Explore the significance of QA in ensuring end-user satisfaction, along with a detailed look at various QA processes such as link QA, demo app testing, and development environment testing.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
QA Process Presented By: Presented By: Sangram Patil Sangram Patil ( (Senior QA Engineer)
Importance of QA QA is focused on end-user satisfaction, ensuring the product s features and functions meet the client s requirements. At the same time, software testing focuses on test cases and their implementation to properly search for defects. Quality assurance helps to identify and prevent possible issues before they appear. In contrast, software testing aims to detect defects and ensure they are fixed.
Block Diagram of Development and QA Process Requirement Analysis Design Development Phase (Implementation) If any bug found QA Process (Testing) Deployment
Process of Pixika QA Link QA (Data Collection) : In link QA we have to check all the fields in the link. In Cropper size and all UI testing we make sure that data should be collected as per the project requirements. Sampling QA : On Average 20-30 Production stitch data from a given form id is provided to QA Team by the Front End team, in an Excel sheet. On each QA link testing needs to be done. On approval of sampling QA, the Front End team initiates with Full Stitch on production data for the given form id. Full Stitch QA: Complete Production stitch data for a given form id is provided to QA Team by the Front End team, in an Excel sheet. As per the Boundary Value Analysis, QA link testing needs to be done. On approval of Full Stitch QA, the Front end team initiates label generation.
Process of Kribado QA Demo App Testing : In demo app testing QA has to check all scale levels testing calculations, Branding logos, Prints and Reference. After the demo app is approved by QA it will be sent to the client for approval once the client approves the demo app we go for production. Production Testing ( Testing + Production Device) : In Production app testing QA has to check all basic flow of scale level testing, calculations, Branding logos, Prints and Reference. Also QA has to verify whether all details from the app are displayed or not on the dashboard. This activity performs two steps first is on the testing device with testing data and the second is on the production device with client data.
Process of DetailMD QA Development Environment Testing : In the Development Environment testing is done on the testing device with dummy testing data. In this phase we have to check app containing with all the requirements of the client or not, and also check whether the details get reflected or not on the dashboard. Production Environment Testing : In the Production Environment testing is done on the Production device with Client testing data. In this phase we have to check app containing with all the requirements of the client or not, and also check whether the details get reflected or not on the dashboard.
Flaws of custom changes Creating a new module or editing an existing module can lead to failure because of a limited time frame. Multiple changes in any of on going project leads to delay in time line or some times failure.
