Today's Updates:

Showing posts with label testing basic concepts. Show all posts
Showing posts with label testing basic concepts. Show all posts

Friday, May 9, 2014

Difference between White Box, Block Box and Gray Box Testing

Difference between White Box, Block Box and Gray Box Testing:

White Box Testing
White box testing strategy deals with the internal logic and structure of the code. White box testing is also called as glass, structural, open box or clear box testing. The tests written based on the white box testing strategy incorporate coverage of the code written, branches, paths, statements and internal logic of the code etc.

In order to implement white box testing, the tester has to deal with the code and hence is needed to possess knowledge of coding and logic i.e. internal working of the code. White box test also needs the

Difference between Verification and Validation with methods of verification process

Verification:-
  1.        In general, Verification is defined as “Are we building PRODUCT RIGHT?” i.e., Verification is a process that makes it sure that the software product is developed in the right way. The software should confirm to its predefined specifications, as the product development goes through different stages, an analysis is done to ensure that all required specifications are met.
  2.        During the Verification, the work product (the ready part of the Software being developed and various documentations) is reviewed/examined personally by one or more persons in order to find and point out the defects in it. This process helps in prevention of potential bugs, which may cause in failure of the project.

Thursday, May 8, 2014

Difference between Software Project and Software Product

Difference between Software Project and Software Product

Project:
If a software application designs for a specific client, then it is called PROJECT. 
OR
If any organization is developing the application according to the client specification then it is called as project

Product:
If a software application is design for multiple clients, then it is called a PRODUCT.

Wednesday, May 7, 2014

V-model in software testing with advantages and disadvantages

V model

V-model is software development model it is improve from the waterfall model. V-model is normally used for manage the software development project in the large company.
V-model is also called verification and validation model (V&V). It has a very intensive testing in order to eliminate the bug/error that may be occur during each stage of development project using V-model.
You can see the picture of V-model as below

Prototype Model or Pilot Model in software Testing

Prototype Model (Pilot Model)

Prototype module is just a demo application to show client, who does not belongs to the IT sector. It just to show how the application looks after completion whether he wants any changes or as it is.
  •         I.            Prototype is a working model of software with some limited functionality.
  •       II.            The prototype does not always hold the exact logic used in the actual software application and is an extra effort to be considered under effort estimation.
  •     III.            Prototyping is used to allow the users evaluate developer proposals and try them out before implementation.
  •     IV.            It also helps understand the requirements which are user specific and may not have been considered by the developer during product design.

Following is the step-wise approach to design a software prototype:

Wednesday, April 23, 2014

Verizon recruiting for “Network Validation Engineer” in April-2014

Verizon recruiting for “Network Validation Engineer” in April-2014

Company Name
Verizon Communication India Pvt Ltd

Job Role
Network Validation Engineer

Job Location
Bangalore, India

Experience
3-8 Years

Education:
BE, B tech, MCA, M Tech, MSC

Saturday, April 19, 2014

Testing Overview and its history

Testing Overview and its history
Overview:
A primary purpose of testing is to detect software failures so that defects may be discovered and corrected. Testing cannot establish that a product functions properly under all conditions but can only establish that it does not function properly under specific conditions. The scope of software testing often includes examination of code as well as execution of that code in various environments and conditions as well as examining the aspects of code: does it do what it is supposed to do and do what it needs to do. In the current culture of software development, a testing organization may be separate from the development team. There are various roles for testing team members. Information derived from software testing may be used to correct the process by which software is developed.
Every software product has a target audience. For example, the audience for video game software is completely different from banking software. Therefore, when an organization develops or otherwise invests in a software product, it can assess whether the software product will be acceptable to its end users, its target audience, its purchasers and other stakeholders. Software testing is the process of attempting to make this assessment.
History:
During the Years 1970-1980 software developers are used to do design, coding and testing the software and at that time there is very less demand for the software or software projects. But after the year 1980 there was huge demand for the software projects in the market. At the time customer’s expectation was more and it become difficult to provide quality or defect free software by the developer alone. So to provide quality software or to satisfy the customer QUALITY and PRODUCTIVITY came into picture. This was the time testing born. And testing and development separated.

Need of Testing



About testing

What: Identifying the defects is called testing
Why: To find the defects
         To provide good quality Software
        To improve the business
        To satisfy the customer and their requirements
When: In SDLC, depending upon which model you are using for your project.
Who: By Test Engineer, By Developers, By Customers and by end-users (the one who is using the software)

How: It will be describe in test plan



Testing basic interview questions
Related Posts Plugin for WordPress, Blogger...