quality control1

Substantial Terms for Software Testing and Quality Assurance

Software Quality Assurance:

Software QA includes the whole software development PROCESS — it is made to be sure that any agreed-up on procedures and standards are followed, improving and monitoring the process, and conviction of the fact, that problems are found and dealt with. It focuses on ‘prevention’.

Quality Assurance determines the quality of processes used to make a quality product. In addition, it is a system of management activities. Quality Assurance is a preventive process, which applies for the whole life cycle and deals with the process.

It is very important for a tester to understand what is the difference between Quality control and Quality Assurance.

Quality control measures the quality of a product. It is a specific part of the Quality Assurance procedure. This corrective process applies for particular product and deals with the product.

Priority and Severity will be assigned for a concrete bug to know the importance of the bug.

Priority: Allows to the developer to understand which bug have to be fixed first.

Severity: How strongly the bug is affecting the application.

Defect: If you found any mismatch, while performing the test case, you will describe it to the development team. It is called defect.

Bug: It will be called bug if developer accepts your defect.

Test case

Test case is a document that includes information about an event, input or action, and an estimated response, to check if a singularity of an application is working properly.

Test condition. The condition is needed to test a feature.

Test script

Test script is the script which is created by an automation tool while recording an application features.

Test data

Test data means the input data (invalid, valid data), which is giving to check the application’s feature whether it is working correctly or not.

Test bed

Test bed means the test environment (software, hardware set up) in which an
application will run exactly.

Baseline document

An approved document and the review is called – a baseline document (i.e) SRS (Software requirement Specification), test plan.

Configuration management:

Configuration management involves the processes used to coordinate, control and track: requirements, code, documentation, change requests, problems, designs, tools, libraries, compilers, patches and changes made to them, and who makes the changes.

Verification:

Verification usually includes meetings and reviews to evaluate plans, documents, code, specifications and requirements. This can be done with issues lists, checklists, inspection meetings and walkthroughs.

Validation:

Validation usually takes place after verifications are completed and includes actual testing.

The term ‘IV & V’ means Independent Verification and Validation.

Walkthrough:

An informal meeting for informational purposes or evaluation is called ‘walkthrough’. Small preparation or no preparation at all is typically required.

Inspection:

An inspection is more formalized than a ‘walkthrough’, usually it includes 3-8 people: a reader, a recorder to take notes and a moderator. Typically inspection focuses on a document such as test plan or requirements spec, and the purpose of it is not fixing anything, but finding the problems and seeing what’s missing. Attendees have to prepare for this type of meeting: anyway, main problems will be found during reading the document. A written report will be the result of the inspection meeting. Despite preparation for inspections is painstaking and difficult work, but it is one of the most cost effective methods of ensuring quality.


TestFort Blog

About TestFort Blog

TestFort blog is an official blog of TestFort QA Lab company and is dedicated to various QA and software testing issues.


4 comments

  1. May 10, 2012 @ 3:43 pm office 2007

    Fantastic issues altogether, you just gained a logo new reader. What could you suggest in regards to your publish that you made a few days ago? Any sure?

  2. June 8, 2012 @ 2:10 pm Steesiree

    My cousin recommended this blog and she was totally right keep up the fantastic work!

    • December 8, 2012 @ 6:00 pm kartalrenault

      Captcha is one of the best techniques against auto bot registration but xrumer will destory it with is astounding power. One of the most typical spam behavior is auto account registration on forums e.g Xrumer. These bots intend to post advertising messages with out manual control and so so quite successfully with xrumer. Tools like Xrumer are dedicated for this purpose. Thus, it is possible to set up captcha against bot registration. Alternatively, setting up anti-spam questions that appear randomly will also be helpful but it real wont work due to the fact xrumer is king. Xrumer

    • April 1, 2013 @ 9:59 pm Celine Sale

      Itˇs actually a nice and helpful piece of info. I am satisfied that you simply shared this helpful info with us. Please stay us informed like this. Thanks for sharing.


Would you like to share your thoughts?

Images are for demo purposes only and are properties of their respective owners.
Old Paper by ThunderThemes.net © 2017

×