Active TopicsActive Topics  Display List of Forum MembersMemberlist  CalendarCalendar  Search The ForumSearch  HelpHelp
  RegisterRegister  LoginLogin


 One Stop Testing ForumTypes Of Software Testing @ OneStopTestingFunctional Testing @ OneStopTesting

Message Icon Topic: incremental testing VS. thread testing

Post Reply Post New Topic
Author Message
tanushree
Senior Member
Senior Member
Avatar

Joined: 04Apr2007
Online Status: Offline
Posts: 2160
Quote tanushree Replybullet Topic: incremental testing VS. thread testing
    Posted: 25Oct2007 at 4:56am
According to Guide to CSTE Common Body of Knowledge, incremental testing refers to 'a disciplined method of testing the interfaces between unit-tested programs as well as between system component'. There are two types: Top-down and Bottom up.

Thread testing 'demonstrates key functional capabilities by testing a string of units that accomplish a specific function in the application'. Thread testing and incremental testing are usually utilized together.

Are they black-box testing or white-box testing? when should the testers perform this kind of testing? and how to use these techniques in practical project?



Post Resume: Click here to Upload your Resume & Apply for Jobs

IP IP Logged
kanagarathinam
Newbie
Newbie


Joined: 18Sep2008
Online Status: Offline
Posts: 1
Quote kanagarathinam Replybullet Posted: 18Sep2008 at 7:04am
what is black-box testing ?
IP IP Logged
kanagarathinam
Newbie
Newbie


Joined: 18Sep2008
Online Status: Offline
Posts: 1
Quote kanagarathinam Replybullet Posted: 18Sep2008 at 7:31am
plz tell me with example.
IP IP Logged
kanagarathinam
Newbie
Newbie


Joined: 18Sep2008
Online Status: Offline
Posts: 1
Quote kanagarathinam Replybullet Posted: 18Sep2008 at 7:32am
what is black-box testing ? plz tell me with example.
IP IP Logged
tossy
Groupie
Groupie
Avatar

Joined: 20Aug2008
Online Status: Offline
Posts: 99
Quote tossy Replybullet Posted: 22Sep2008 at 4:00am
Originally posted by kanagarathinam

what is black-box testing ? plz tell me with example.



Black Box Testing is testing without knowledge of the internal workings of the item being tested.  For example, when black box testing is applied to software engineering, the tester would only know the "legal" inputs and what the expected outputs should be, but not how the program actually arrives at those outputs.  It is because of this that black box testing can be considered testing with respect to the specifications, no other knowledge of the program is necessary.  For this reason, the tester and the programmer can be independent of one another, avoiding programmer bias toward his own work.

IP IP Logged
pras
Newbie
Newbie


Joined: 23Sep2008
Online Status: Offline
Posts: 1
Quote pras Replybullet Posted: 23Sep2008 at 6:41am

Black box testing takes an external perspective of the test object to derive test cases. These tests can be functional or non-functional, though usually functional. The test designer selects valid and invalid input and determines the correct output. There is no knowledge of the test object's internal structure.

This method of test design is applicable to all levels of software testing: unit, integration, functional testing, system and acceptance. The higher the level, and hence the bigger and more complex the box, the more one is forced to use black box testing to simplify. While this method can uncover unimplemented parts of the specification, one cannot be sure that all existent paths are tested.

IP IP Logged
pras
Newbie
Newbie


Joined: 23Sep2008
Online Status: Offline
Posts: 1
Quote pras Replybullet Posted: 23Sep2008 at 6:44am

In this technique, we do not use the code to determine a test suite; rather, knowing the problem that we're trying to solve, we come up with four types of test data:

  1. Easy-to-compute data
  2. Typical data
  3. Boundary / extreme data
  4. Bogus data

For example, suppose we are testing a function that uses the quadratic formula to determine the two roots of a second-degree polynomial ax2+bx+c. For simplicity, assume that we are going to work only with real numbers, and print an error message if it turns out that the two roots are complex numbers (numbers involving the square root of a negative number).

We can come up with test data for each of the four cases, based on values of the polynomial's discriminant (b2-4ac):

Easy data (discriminant is a perfect square):

a b c Roots
1 2 1 -1, -1
1 3 2 -1, -2
 

Typical data (discriminant is positive):

a b c Roots
1 4 1 -3.73205, -0.267949
2 4 1 -1.70711, -0.292893
 

Boundary / extreme data (discriminant is zero):

a b c Roots
2 -4 2 1, 1
2 -8 8 2, 2
 

Bogus data (discriminant is negative, or a is zero):

a b c Roots
1 1 1 square root of negative number
0 1 1 division by zero
 

As with glass-box testing, you should test your code with each set of test data. If the answers match, then your code passes the black-box test.

IP IP Logged
Post Reply Post New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum



This page was generated in 0.125 seconds.
Vyom is an ISO 9001:2000 Certified Organization

© Vyom Technosoft Pvt. Ltd. All Rights Reserved.

Privacy Policy | Terms and Conditions
Job Interview Questions | Placement Papers | Free SMS | Freshers Jobs | MBA Forum | Learn SAP | Web Hosting