Skip to main content

What is Verification in terms of Software Testing?

By
As the meaning of the word verification means to verify something. In software testing, it doesn’t mean something different. In it, verification makes sure that the user/customer will get the desired product (software) with its desired specifications (functionality).
ü It is a part of the software development cycle and it is done for the beginning of the development process by software tester.
ü Software Verification is a manual process i.e. testers do it manually or we can say that design and code are checked (verified) by testers manually.
ü For software verification, reviews, inspection, meetings and walkthrough are conducted for the assessment of the plans, codes, specifications and requirements.
ü It provides the solution of the question: are we developing  the product in a right manner?

Suppose you have a project of building a chair, then you will have a verification that it is strong or not, all the four legs are equal or not, if it is not so then the project is not developed in the right manner. Similar is the case with software project (product/application) to prevent it from failure due to any defect.

What does the Capability Maturity Model (CMMI) say about Verification in Software testing?
CMMI defines software verification as software evaluation process that finds whether a given development phase product can withstand the conditions imposed at the starting of that phase [IEEE-STD-610].

Benefits from Software Verification:
1. More Verification makes the software more accurate during development phase as it reduces the number of defects found.
2. More verification makes the software more stable.
3. Verification develops the product in a way that it withstands the customer requirements.

Approaches of Verification:
Software Verification follows basically two defined approaches:
1. Dynamic Verification - also known by the name of               Tests/Experimentation. Bugs are found out using this.
2. Static verification- the other name is Analysis. It proves the correctness of the application.

 Dynamic Verification:
It is dynamically done during software execution.
The tests are divided in the three categories namely,
1. When a single function or class is checked, it is called Test in small (or unit Test).
2. Test done on  the group of classes is called Test in large.
3. Test done for checking software acceptance is called Acceptance Test.
Static Verification:
In this code is checked for seeing whether software meets requirements or not.

In this measured data results and observed data results are compared with calculated expected values to see how much they withstand standard requirement.
Labels:

Comments

Post a Comment

Popular posts from this blog

Steps To Hunt the Bugs Successfully

By
The testers should catch the bugs in software that they’re testing. Testers should try to catch as several vital bugs as soon as possible. Catching the crucial bug earlier on Product-Life-Cycle can save the Projects from financial losses & mitigate the risks as compared for catching the same at a later stage in SDLC. Steps to hunt the bugs: Sometimes it’s useful to break the rules: The following test cases, which were predefined a tester can miss the bugs so it makes it impossible’s to provide the product i.e. 100 percent bug free. If you-follow pre-determined test cases you risks becoming blind to outside the bugs. A first secret is to check the functionality under the test. It’ll be an effective channel to discover the more bugs, because functionality is not generally covered by the test cases. Examine the patterns: You might have noticed that the bugs can be often met in the groups, one can call them-gregarious. The testing a new but the similar functionality...
Post a Comment
Read more

Cross browser testing Tools

By
Cross Browser testing It is a process to test the web apps across multiple browsers. It involves the checking compatibility of the app across multiple web browsers & ensures that your web app’s works correctly across different web browsers. Tools for Cross Browser Testing Browser shots: The browser shots might be most exhaustive cross browser-testing tool that exists. Browser Shots includes all of most popular-browsers, like Firefox, Chrome, & Safari, along with the tons of another browser’s that might sound unfamiliar, like Sea Monkey, Flock, & Iceape. You can adjust the resolution, color-settings, & even Flash and JavaScript settings. Cross Browser Testing: It allows users to test their websites with over the hundred resolution or browser and Operating System combinations. This also has support to mobile web-browsers, which is crucial because the web traffic is making shift from the primarily desktop computer users to primarily mobile ...
Post a Comment
Read more

Mobile Application Testing: Strategy for Development

By
There are a huge number of demands and lots of competitions in the mobile application industries. In that demands and competitions, the mobile application testing has become more important. The testing phase of the mobile application testing looks like evil between the creative process and excitement of new products in the market. According to the survey, “In US, on an average 2-3 hours per day people spends their time on smartphones and tablets. On that time, they spent 80% on mobile application and remaining 20% on web applications.” Few list of key factors for successful mobile application testing strategies are: Selection of Device for Testing : Before introducing the mobile application test activities, first select the devices for testing the application. Selection decision is very important because only devices can help to targets maximum numbers of the customers for accessing the application. There are two parts for device selection: §   Device Model ...
Post a Comment
Read more