Tag Archive

Below you'll find a list of all posts that have been tagged as "qa"

What is Difference Between Quality Assurance vs Quality Control?

Many times the terms QA (Quality Assurance) and QC (Quality Control) are interchangeably used by people, especially those who are new to the field of Software Testing, however, this is incorrect. Both QA and QC are two unique approaches to improving the quality of the software under development and they are at the heart of Software Development. But both play a vital role in test automation strategy. Quality Assurance and Quality Control are related to each other, but they are originated based on different needs. Quality Assurance is more of a process oriented approach, and it focuses on the prevention of defects, whereas Quality Control is a product oriented approach, and it focuses on defect identification and fixes. The Difference ISO defines Quality Control as a part of quality management focused on fulfilling quality requirements, and Quality Assurance as a part of quality management focused on providing confidence that quality requirement will be fulfilled. There is a need to have systematic planning of all the processes in place, and these, in terms of Quality Assurance need to be demonstrated in order to provide the confidence to the quality of the software. A Quality Assurance review would focus on the process elements of a project e.g. ‘Are all the necessary and sufficient details captured in the requirements?’. Defining the methodology and developing standards are some of the important examples that can be mentioned under the domain of Quality Assurance. Quality Control requires the same; however, here the focus is more on the systematic planning of the operational techniques. In case of specific deliverables, Quality Control would mean finding defects in it e.g. ‘Are the right details captured in the requirements?’ There can be a blurred line between who should be responsible for Quality Assurance and who for Quality Control, and this would vary from organization to organization and from situation to situation within an organization, however, while both of these can be in-house, and can be done by a single team as well, an external Quality Assurance function definitely throws a clearer light on whether QA is being implemented correctly or not. Again, this would depend upon how mature the organization’s Quality Assurance or Project Management practices are, and how exactly the organization wants to enhance them in the days to come. Inculcating these practices right from the beginning to the best level possible can help an organization polish their Quality Assurance and Quality Control practices, and implement them fully in-house to avoid external dependency. Below is a comprehensive table enlisting the clear differences between Quality Assurance and Quality Control, for better understanding of the reader: Quality Assurance Quality Control Quality Assurance is the process of managing the quality of the software under development Quality Control is the set of methods used to verify the quality of the output delivered by the software QA is more of a comprehensive activity in which establishing long-term good quality management systems – and assessing that those systems help us conform to the customer requirements – is done. Thus, QA is process-oriented. QC is more of a product-specific activity in which tools and equipment are used to confirm that the customer’s requirements are continually met. Thus, QC is product-oriented. QA is proactive. It identifies the weaknesses in processes beforehand. QC is reactive. It identifies the defects in the software system after its development, and then fixes them as required. QA prevents the occurrence of issues, bugs, or defects in the system. Thus, it is more managerial in nature. QC identifies the issues, bugs, or defects in the system, and then works towards fixing them. Thus, it is more corrective in nature. QA requires manual checking of documents or files, such as Quality Plans or Test Plans. QC is often done by automatically running the program or software, and then physically measuring if the system runs according to the prescribed requirements. QA does not involve executing the program or code. QA always involves executing the program or the code being tested. Every person who is part of the Software Development is essentially responsible for the overall Quality Assurance of the product. Testing Team is primarily responsible for conducting the Quality Control. QA is a type of Verification, because it involves checking if you’re doing the right thing in the right way. QC is a type of Validation, because it involves checking if what is done is right. QA involves planning for a process. It is basically defining standards and processes to be followed in order to meet the customer requirements. QC involves taking action towards the process by executing it. It is basically ensuring that the necessary standards or requirements are met. Examples of a few QA Activities: – Process Definition and Implementation – Audits – Training Examples of a few QC Activities: – Code Reviews – Test case development – Software Testing – Defect fixing There can be a blurred line between who should be responsible for Quality Assurance and who for Quality Control, and this would vary from organization to organization and from situation to situation within an organization. But, while both of these can be in-house, and can be done by a single team as well, an external Quality Assurance service provider definitely throws a clearer light on whether QA is being implemented correctly or not. Again, this would depend upon how mature the organization’s Quality Assurance Services or Project Management practices are, and how exactly the organization wants to enhance them in the days to come. Inculcating these practices right from the beginning to the best level possible can help an organization polish their Quality Assurance and Quality Control practices, and implement them fully in-house to avoid external dependency.

Aziro Marketing

qa quality-assurance

Web Test Automation: 8 Testing Phases That You Should Know About

Web-based systems have become popular to develop business-critical applications. Testing teams in every company often apply the best manual testing approach to curate these applications. Most of the time, some of the other glitches crop-up post the applications go live. Here is your phase-wise guide to implement Web Test Automation, increase the coverage and effectiveness of the manual testing process. and ensure zero application defects.Web Automation Testing PhasesManual TestingWrite manual test case, per the manual testing process.Execution of Manual Test CasesExecute Manual Test Cases, unearth defects, and fix them to get the stable Application Under Test (AUT) for automation.Feasibility studyUnderstand the test requirements and identify the feasible test case candidates for automation. These are the test cases which are generally complex to execute manually, repetitively and mostly from Regression Test Suite.Automation Tools SelectionSelect the ideal choice for test automation programming language – Java, Javascript or Python. The languages enable quick and easy development of test scripts.Select a UI automation tool depending on the development technology used for the Application Under Test (AUT). You can go for Selenium Web Driver and ProtractorUnit Test FrameworkTestNG, Jasmine, Mocaha, Karma or PyTest is used as a unit test framework.Automation Testing FrameworkUse a suitable Test Framework like Page Object Model to build the Automation FrameworkUse Extent Reports, Allure Reports, etc. for the Test Report generationUse Maven for Dependency Management.Use Jenkins for continuous integration and delivery.Page Object Model (POM) Architecture using Test NGAutomation TestingWrite Automation Test scripts for the selected manual test cases.Create various Test Suites like Regression, Smoke, etc.Do Cross Browser testing leveraging Docker containers on Chrome, Firefox.Send the generated Test Reports via Email to concerned stakeholders.Example of a Test Report Automation Maintenance:Leverage Automation Team to maintain the Automation Test scriptsBenefits of Automation TestingFast: Runs tests significantly faster than human users.Repeatable: Testers can test how the website or software reacts after repeated execution of the same operation.Reusable: Tests can be re-used on different versions of the software.Reliable: Tests perform precisely the same operation each time they are run thereby eliminating human error.Comprehensive: Testers can build test suites of tests that covers every feature in the software application.Programmable: Testers can program sophisticated tests that bring hidden information.Test Automation Services for enterprisesOrganizations need to evolve their products constantly in order to stay ahead of their competitors. For businesses whose focus is on using applications to run their business more effectively, they need a better, more cost-efficient way of ensuring that business processes will continue to operate properly when you implement software changes. Aziro (formerly MSys Technologies) is a leading provider of testing software and services for enterprises. Our test automation services enable companies to reduce operational costs and improve product performance.

Aziro Marketing

automation testing qa qa automation test-automation testing automation tools Web Automation Testing web test automation

Q&A on Mobitaz Android Test Automation Webinar

On the fifth of June, 2014, we conducted a webinar on Mobitaz, Aziro (formerly MSys Technologies)’s Android test automation tool. In this webinar, a number of professionals from various companies on testing and general quality assurance participated. Needless to say it was a big success. It can be challenging for a quality analyst to choose the right mobile-functional-testing tool for his testing purposes. Manual testing or the use of automation tools with limited testing capabilities can be a hindrance in expediting the QA process. Mobitaz (Aziro (formerly MSys Technologies) Android test automation tool) team at Aziro (formerly MSys Technologies) explored the need for a device- and an OS-agnostic mobile testing tool which can give the assurance to a QA team that testing isn’t compromised and too much time is not taken in a QA cycle. Discussions made in the Mobitaz webinar will bring a massive change in the traditional automation technique/solutions. Some of the interesting discussions initiated by the quality assurance personnel from leading companies are as follows: Parallel execution Question: Does it mean that I can run a test made for Kit Kat on Gingerbread and ICS at the same time? Answer: Yes. Concurrent playback on Kit Kat, Gingerbread and Ice Cream Sandwich can be achieved through Mobitaz. Question: So, Mobitaz adapts to different android objects that differ between OSes? Like progress bar between Gingerbread and Kit Kat? Answer: Yes. This is something unique about Mobitaz. The tool can record a test case once and play it back across any Android device or OS version. Mobitaz has the intelligence to recognize objects with different Android versions. Through this capability, it can make successful parallel test executions. Advantages Q: What are the advantages of this Android test automation tool over other mobile automation tools in the market? A:We compare Mobitaz directly with other tools which offer a lab-based solution. A few of the advantages over other mobile testing tools are: Support for Android Custom components Android Web-View components Parallel execution Testing on real devices without rooting Detailed reporting with easy option to export and share to PDF format Key measurements of resources such as battery, CPU, memory etc. Mobile functional testing for Android versions from Gingerbread to the latest version Simplified licensing model Cost-effectiveness Script-less Testing Q: Does Mobitaz Android test automation tool require any scripting knowledge to create, execute, and generate reports? A: No. Mobitaz is a script-less test automation tool and does not require any programming knowledge for functional testing of mobile apps. Mobitaz has intelligence to manage test cases, through features such as Object Repo, Test Case Editor, Reports, etc.

Aziro Marketing

EXPLORE ALL TAGS

Ansible Test Automation

application containerization

applications

Application Security

application testing

artificial intelligence

asynchronous replication

business intelligence

Cloud Cost Optimization

cloud devops

Cloud Infrastructure

Cloud Interoperability

Cloud Native Solution

Cloud Storage Security

Codeless Automation

Cognitive analytics

Configuration Management

container world conference

continuous-delivery

continuous deployment

continuous integration

data backup and recovery

Descriptive analytics

Descriptive analytics tools

Digital Transformation

dockercon 2019 san francisco

end-to-end-test-automation

High Performance Computing

icinga for monitoring

Image Recognition 2024

kubernetesday bangalore

Low-Code No-Code Platforms

mobile-application-testing

mobile-automation-testing

Predictive analytics tools

prescriptive analysis

Rapid Application Development

raspberry pi

RDMA

real time analytics

realtime analytics platforms

Real-time data analytics

Recovery

Recovery as a service

recovery as service

rsa

rsa 2019

rsa 2019 san francisco

Selenium Test Automation

selenium testng

serverless

Serverless Computing

Site Reliability Engineering

software defined storage

software-testing

software testing trends

software testing trends 2019

storage virtualization

support

Synchronous Replication

testing automation tools

thought leadership articles

trends

tutorials

ui automation testing

ui testing

ui testing automation

vCenter Operations Manager

vmworld 2019 san francisco

VMworld 2019 US

vROM

Web Automation Testing

web test automation

WFH

LET'S ENGINEER

Your Next Product Breakthrough

Book a Free 30-minute Meeting with our technology experts.

Aziro has been a true engineering partner in our digital transformation journey. Their AI-native approach and deep technical expertise helped us modernize our infrastructure and accelerate product delivery without compromising quality. The collaboration has been seamless, efficient, and outcome-driven.

CTO

Fortune 500 company

Tag Archive

What is Difference Between Quality Assurance vs Quality Control?

Web Test Automation: 8 Testing Phases That You Should Know About

Q&#038;A on Mobitaz Android Test Automation Webinar

EXPLORE ALL TAGS

LET'S ENGINEER

Your Next Product Breakthrough

Q&A on Mobitaz Android Test Automation Webinar