• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Rob Spoor
  • Junilu Lacar
  • paul wheaton
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Scott Selikoff
Bartenders:
  • Piet Souris
  • Jj Roberts
  • fred rosenberger

testing

 
Ranch Hand
Posts: 8944
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
what are the different types of testing?
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Unit testing
Integration testing
System testing
Functional testing
Performance testing
Load testing
Stress testing
Assembly testing
etc etc.
Some of these are specializations of other types of testing, some are synonyms, and none of these means exactly the same thing in two different organisations
 
Pradeep bhatt
Ranch Hand
Posts: 8944
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks Lasse
Where does black and white box testing come into picture?
 
Lasse Koskela
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Ah, forgot those. "Black-box testing" is the kind of testing where you poke the application using its published interfaces (e.g. UI, a networking protocol, etc.) while "white-box testing" is the kind where you test that the internals work as expected (e.g. unit testing). Typically, the white box testing starts before black box testing simply because you generally have at least some code before you've got a working user interface to test against. However, some folks start writing and executing the black box test (functional tests) at the same time as writing the white box tests.
 
Pradeep bhatt
Ranch Hand
Posts: 8944
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Can I say that White box testing is done only in Unit testing?
 
Pradeep bhatt
Ranch Hand
Posts: 8944
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What is a unit? Is it a class?
 
Ranch Hand
Posts: 280
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Don't forget regression testing
A Unit is a component, class or function. Its the way the design was broken down before coding begins.
 
Pradeep bhatt
Ranch Hand
Posts: 8944
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello
Is system testing a black box testing?
 
Ranch Hand
Posts: 168
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
yes
 
Author
Posts: 70
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Pradeep Bhat:
Hello
Is system testing a black box testing?


it all depends on your point of view... ;-) What is black box testing for someone is white box testing for someone else! Everything is relative (hey, I heard that somewhere... ;-) )
 
Pradeep bhatt
Ranch Hand
Posts: 8944
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Diff b/w load & stress testing?
 
Lasse Koskela
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Pradeep Bhat:
Diff b/w load & stress testing?


In stress testing, you slowly choke the application by denying resources (CPU, memory, etc.) to see a) where's the limit, b) whether some defects show up in this extreme situation.
In load testing, you're running a more reasonable load and measure certain properties such as transactions per second, throughput, response times, etc. and to make sure that the application will not crash after a couple of hours.
Disclaimer: there might be other nuances to these terms, which I'm not aware of. Heck, I might have even posted outright flawed statements here...
 
Pradeep bhatt
Ranch Hand
Posts: 8944
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
How to generate test data? Any guidelines to be followed.
 
Lasse Koskela
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Pradeep Bhat:
How to generate test data? Any guidelines to be followed.


The golden rule is test on the edges meaning that there's not much value in testing "add(1, 2)", "add(1, 3)", "add(1, 4)" and "add(1, 5)" because if the first one works, it's highly likely that the rest work too. Then again, add(1, 0) or add(1, -1) might very well break because programmers make mistakes more easily when dealing with values on "the edge". In this case, the edge is zero.
Another golden rule is test with malicious input, i.e. don't trust the user. For example, you should always test that the user can't mess up your database by submitting a partial SQL statement as part of a form's values. Similarly, for a given input element, you should test with expected input as well as unexpected input--meaning empty strings, sp3c!alch@r@cte<rs>, etc.
 
Ranch Hand
Posts: 3404
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
User Aceptance Testing, wherever you may place it.
With XP, it is an on-going process.
regards
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic