Last week, we had the author of TDD for a Shopping Website LiveProject. Friday at 11am Ranch time, Steven Solomon will be hosting a live TDD session just for us. See for the agenda and registration link
  • 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:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
Bartenders:
  • Piet Souris
  • Himai Minh

Type of Tests!!

 
Ranch Hand
Posts: 176
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Folks,
I would like to know what type of tests should an application undergo such that it becomes perfect application.Please refer any URLs for the same.
Thanks in Advance.
Ravi
 
Ranch Hand
Posts: 1970
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Ravi Kumar R.S:
Hello Folks,
I would like to know what type of tests should an application undergo such that it becomes perfect application.


No application, of any useful size, will ever be perfect. By good testing, assertion and the like, one can make it good enough, where your definition of "good enough" can vary, but can never be perfection!
By doing lots of assertions and unit tests (e.g. JUnit), you ensure that your code is good, at the micro level. It is much easier (cheaper) to find bugs at this level than later, say in integration testing. Such testing must test unusual conditions, as well as the most typical conditions.
As well as functional testing ("does it do the right thing?"), you may need non-functional testing ("is it fast enough?", "can it handle 1000 users?" etc.).
 
Ravi Kumar Ravuru
Ranch Hand
Posts: 176
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Peter,
Thanks for the response.Can you refer any good urls for the same.
Ravi
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think the two most important types of tests are:
- unit tests, telling the developers wether the code works as he intended it to. In my experience, those tests are best written using the "test-first" technique, as this leads to a very testable design and a good test coverage. See http://c2.com/cgi/wiki?TestDrivenDevelopment
- acceptance tests, written by the "Customer", showing that the system is doing what the customer wants it to do. These tests also can serve as a rather non-ambiguous specification to the developers. As with unit tests, it is critical get these tests run early and often. http://c2.com/cgi/wiki?AcceptanceTest
There are teams using these two approaches reporting formidable success - some even forget how to use the bug database some months after adopting these techniques...
See also http://c2.com/cgi/wiki?ContinuousIntegrationRelentlessTesting on how to put things together...
[ January 14, 2003: Message edited by: Ilja Preuss ]
 
"The Hood"
Posts: 8521
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
We are required to undergo these formal testing steps to implement any production code:
(after normal debugging testing)
Unit testing
Integration Testing
Regression Testing
System Testing
User Acceptance Testing
possibly also (these are usually handled separately because they require different tools):
Load testing
Performance testing
No URLs to offer though. All my references are internal to the company .
[ January 14, 2003: Message edited by: Cindy Glass ]
 
Ranch Hand
Posts: 265
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
is it availble any Unittesting software except Junit!!if yes please refer me
 
Ranch Hand
Posts: 775
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think by comparing Cindy and Ilja's responses, you can see that the answer will vary, if you are looking for the "which kinds of tests should I write" type of advice. If you want theoretical categories of testing, then you'll probably want to find a few decent books on QA.
The real problem you'll run into is that you'll find that both (a) different people use different terms for the same testing category, and (b) any given term may be used by different people to mean completely different testing categories.
For example:
  • black-box test
  • functional test
  • acceptance test
  • validation
  • verification
  • usability test


  • There are at least three different testing concepts in that list, but you'll hear all of them used in different ways. Even worse, some of them can have different implications to a QA person and to a project/contract manager.
     
    Self destruct mode activated. Instructions for deactivation encoded in this tiny ad.
    free, earth-friendly heat - a kickstarter for putting coin in your pocket while saving the earth
    https://coderanch.com/t/751654/free-earth-friendly-heat-kickstarter
    reply
      Bookmark Topic Watch Topic
    • New Topic