SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 9 of 9
  1. #1
    Junior Member
    Join Date
    Apr 2004
    Location
    Bangalore
    Posts
    29
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Testing in general

    Could any body please tell me what is static testing?
    Another question I have is as follows:
    We talk of smoke,black box, white box, unit, funtional,regression, stress testing etc. Can you find time to do all?
    Doesn't one testing overlap the other?
    What is the difference between regression & functional testing?

    Thank you for reading.
    Thanks to all who reply.
    Brain

  2. #2
    Member
    Join Date
    Apr 2004
    Location
    India
    Posts
    37
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Testing in general

    static testing?

    static testing is the technical reviews of the architecture, HLD, LLD, and then code walkthros etc conducted during the development process.
    though this is not 'testing' as such, this is a definitely a QC activity and so many issues arise and are solved at this point itself.

    Can you find time to do all?

    depends on -
    1. the time given to u
    2. your testing efficiency, skills, other resources etc
    3. your testing process (whether u get involved in the end phase or in the beginning of the development process)

    Doesn't one testing overlap the other?

    each level/type of testing has its own importance. of course overlap is there... e.g., u do the unit and integration testing, and after the bugs have been fixed at these levels, u go for functionality testing. it's quite possible that some of the bugs that should have been found at unit / integration level are found during functionality testing. but imagine u r directly going for the functionality testing... , u simply cant, the product will be very buggy. it's a time waste since u dint properly plan the unit and integration testing.
    again, stress testing and volume testing overlap, but each has it's own purpose to serve.
    hope u get the idea.

    What is the difference between regression & functional testing?

    this is no way to compare..
    regression testing is testing the functionality of the product such that, the certain bug fixes, feature enhancements or new features, have NOT resulted in bugs elsewhere. it's not a "re-testing" though.

    [ 05-10-2004, 10:54 PM: Message edited by: ssk_qa ]

  3. #3
    Junior Member
    Join Date
    May 2004
    Location
    usa
    Posts
    4
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Testing in general

    Hi brain,
    Answering the last one...functional testing is black box testing, where as regression is both white/glass box as well as black box testing.

    Smoke testing/sanity/confidence testing involves testing major functionality of the application

    Regression is re-testing whenever there is change of code. (this includes glass and black box )

    Function testing is testing each and every functionality of the application.

    White box or glass box testing includes unit testing and integration testing. Testing here involves testing the code directly. Unit testing is testing of individual applications.

    Smoke Testing, Function Testing and Regression are black box tests. (Except regression involves white box also)

    Stress Testing involves application or program's response time during peak activities.

    I may contradict others...but in a way i am right.

    Hope I answered all.....
    good luck!!
    KK
    SAP Certified in BIW v3.0b
    Cognos Certifed in Reportnet v1.02

  4. #4
    Senior Member
    Join Date
    Apr 2003
    Location
    Wisconsin, USA
    Posts
    5,338
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Testing in general

    I disagree slightly with the definition of stress testing above. Stress testing doesn't just involve the application response time during peak activities. It involves the entire system response time during peak activities. It is very possible, and probable, that during stress testing, you will pick up on hardware tuning issues that have nothing to do with the application.

    Also, unit testing and integration testing is not always white box. It most often is, but it doesn't have to be. Just as regression and functional testing is most often black box, but doesn't have to be. Don't get black box and white box testing mixed up with regression, functional, integration, etc. Unit, integration, functional, regression are probably best called test phases, whereas white box and black box are types of tests, or maybe better called "ways of testing".

  5. #5
    Moderator
    Join Date
    Sep 2001
    Location
    Boston, MA
    Posts
    4,348
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Testing in general

    Originally posted by mohankk:

    Stress Testing involves application or program's response time during peak activities.
    <font size="2" face="Verdana, Arial, Helvetica">Stress testing is typically where you push a system to its breaking point. You want to apply heavy load to a system and see how it reacts. This will point out the most vulnerable components of your system (OS, application, module, hardware, infrastructure) and also see how it recovers from these situations.

    This is slightly different from what most people call Load or Performance testing, which is what you seem to describe. This involves benchmarking throughput and latency (response times) of transcations when a system is under various states of load (including peak load).

    I'm sure there are many variations on these and different people call them different things. But those seem to be the most common ways the terminology of "load" and "stress" testing are used.
    Corey Goldberg
    Homepage: goldb.org
    Twitter: twitter.com/cgoldberg
    Google+: gplus.to/cgoldberg

  6. #6
    Junior Member
    Join Date
    Apr 2004
    Location
    usa
    Posts
    26
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Testing in general

    Static Testing is when the code is examined without being executed.
    Dynamic testing is when code is executed without going through the program line by line.
    White box testing is mostly static testing.Static testing can be done by the compiler or by coders.
    Black box testing is mostly dynamic testing, you give input and check the output.

  7. #7
    SQA Knight
    Join Date
    Jan 2002
    Location
    Highlands Ranch, CO, USA
    Posts
    2,860
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Testing in general

    Static Testing is the process where you play "computer" or a tool does "static" analysis of the code. This is not done with compiled code. This is typically done at the code level (code reviews/walkthroughs, Cyclomatic Complexity analysis, COCOMO, etc.). This is considered a "White" Box style test, you are inside of the code/function/module itself and are focused on the "internal" processing that takes place (logic processing, data manipulation, etc.)

    Dynamic Testing is the process where you are using compiled live code. In this you have a tool hooked up "monitoring" the code as it is executed. This finds things such as memory usage (memory leaks), path coverage (what logic paths or functions call pairs are most used), API errors (call pair problems). This is typically a white box style test. But is also a "Black" box style test (you don't watch what goes on at the low level, you only care about process flow between modules/functionality at the system level).

    As far as the "boxes" of testing the simplest what to think of it is this: White Box means you look at what goes on inside of each piece, Black Box means you look at what goes on outside (between) of the pieces. Also, I tend to think like Dr. Boris Beizer: "There are no boxes, get out of the box".

    Regression testing has two facets to it. First, testing of the unchanged portion of the system to ensure the system behaves as it did before (this includes defect fixes from before). Second, that the portion of the code that had a fix done is correct and that it did not affect any peripherial areas in an adverse manner (meaning it did not create new defects). This is a type of Functional test.

    Functional testing is what people typically think of as "new" functionality testing/validation. This type of test is done to ensure the "functionality" behaves as expected (according to Requirement Spec., or Use Case). This can be done in a positive style test (happy path) and negative style test (error injection and handling).


    Load Tests
    -----------
    Breaking Point Test - Load test done to find the "breaking" point of the server/system. Typically a "lemming" type test where you continually add more and more users (usually of the same profile type) until the system "jumps off the cliff" and breaks (severe degradation or a crash).

    Performance Test - Load test done to determine the performance (typically timing) of a web page or object or transaction or server (web, app., database, firewall, etc.). This is done using typical load levels (average usage level and/or peak level) to determine how well the system is doing during normal or above normal usage.

    Stress Test - Load test done over a period of time (2 hrs., typical day period) to determine if the system is robust or not, or a test involving processing of large amounts of data to determine capacity (sometimes called Volume Test). This can be used to find processing bottlenecks due to continous usage (memory leaks, etc.) or capacity limitations (tuning aspects).

    Scalability Test - Load Test done to determine performance at increasing levels of capacity. Run a performance or stress test at varying levels (for example; 1000 users, 2500 users, 5000 users, 10000 users for a web site) to do a comparative analysis of these different load levels. How well does the system respond at each level and in comparison between them.

    Thats my take on it all, after 17 plus years of doing this type of work. Have I had time on a project to do it all. Nope, you sometimes get a chance to do a bit of each piece or combination. But typically it is only one or two pieces due to time and resource constraints.

    Jim
    Jim
    -------------------------------------------
    For all the general stuff to know about QA/Test go here http://www.softwareqatest.com/

  8. #8
    Senior Member
    Join Date
    Feb 2002
    Posts
    524
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Testing in general

    To expand on the Google thing, if you type "define:" before a term, you get a number of definitions for that term. For example, type "define: static testing" and you get "Testing of an object without execution on a computer" as one of the results.

  9. #9
    Junior Member
    Join Date
    Apr 2004
    Location
    Bangalore
    Posts
    29
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Testing in general

    Hello All,

    Thank you all for being so helpful.
    Charles Reace, I will keep this in mind the next time I ask a question. Sorry for the goof up.
    Brain

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 8.82%
vBulletin Optimisation provided by vB Optimise v2.6.4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.2.8 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 12:25 PM.

Copyright BetaSoft Inc.