some cognition on volume testing,stress testing and performance testing
2006-12-10 00:33
393 查看
As you know,I've talked about stress testing.Recently,I read volume testing and performacne testing.I found that among these three concepts have some small differences.The important thing is destinguishing them is better for us to design test cases.So let's start.
At first,volume testing is similar with stress testing which I've refered in an article.Actually,I didn't understand at that time at all.Now I have a deep cognition on it.It is a program that is supposed to handle files spanning multiple volumes,enough data are created to cause the program to switch from one volume to another.In other words,the purpose of volume testing is to show that the program cannot handle the volume of data specified in its objectives.I think we must prepare lots of test data before implement this test.Therefore volume testing being obviouly expensive,both machine and people time,one must not go overboard.However,every program must be exposed to at least a few volume tests.
So what is the difference between them?I claim that for stress testing the important thing is loading vast data simultaneously or over a short span of time.Take for example,for a system which must have lots of different functions,we can test its different functions at same time.However,this is an aspect of stress testing.An additional stress test may occur when we know the limit of a program.Except testing the limit of it, we also need to test what will happen when some unexpected data entered,maybe that overrun the boundary.On the other hand,volume testing is test from one volume to another.
At last I want to talk about the difference between stress testing and performance testing.Performance testing is test some specific performance or efficiency objectives,stating such properties as response times and throughput rates under certain workload and configuration conditions.That will apparent,certain workload is the basis of this test.The purpose of it is to test those specific performance or objectives.Therefore,test case is devised that attempt to verify whether the program eligible for its objectives.Additional,I think we can take advantage of these two kind testing together.For example,we can test some extra performances under plenty data after we test them separately.I think that is a good guarantee for system to make sure its quality.
Above these are some cognition on volume testing,stress testing and performance testing.I use for some reference from the book named The Art of Software Testing,and add some own view.I also have some question about volume testing.Actually,I'm not very clear for the meaning of volume.It means different test environment or different kind of data.I'm confused on it.So if you know it,please leave your advise.I'm really appreciate you.Thank you so much!
At first,volume testing is similar with stress testing which I've refered in an article.Actually,I didn't understand at that time at all.Now I have a deep cognition on it.It is a program that is supposed to handle files spanning multiple volumes,enough data are created to cause the program to switch from one volume to another.In other words,the purpose of volume testing is to show that the program cannot handle the volume of data specified in its objectives.I think we must prepare lots of test data before implement this test.Therefore volume testing being obviouly expensive,both machine and people time,one must not go overboard.However,every program must be exposed to at least a few volume tests.
So what is the difference between them?I claim that for stress testing the important thing is loading vast data simultaneously or over a short span of time.Take for example,for a system which must have lots of different functions,we can test its different functions at same time.However,this is an aspect of stress testing.An additional stress test may occur when we know the limit of a program.Except testing the limit of it, we also need to test what will happen when some unexpected data entered,maybe that overrun the boundary.On the other hand,volume testing is test from one volume to another.
At last I want to talk about the difference between stress testing and performance testing.Performance testing is test some specific performance or efficiency objectives,stating such properties as response times and throughput rates under certain workload and configuration conditions.That will apparent,certain workload is the basis of this test.The purpose of it is to test those specific performance or objectives.Therefore,test case is devised that attempt to verify whether the program eligible for its objectives.Additional,I think we can take advantage of these two kind testing together.For example,we can test some extra performances under plenty data after we test them separately.I think that is a good guarantee for system to make sure its quality.
Above these are some cognition on volume testing,stress testing and performance testing.I use for some reference from the book named The Art of Software Testing,and add some own view.I also have some question about volume testing.Actually,I'm not very clear for the meaning of volume.It means different test environment or different kind of data.I'm confused on it.So if you know it,please leave your advise.I'm really appreciate you.Thank you so much!
相关文章推荐
- mySAP Tool Bag for Performance Tuning and Stress Testing
- Difference Between Performance Testing, Load Testing and Stress Testing – With Examples
- Difference Between Performance Testing, Load Testing and Stress Testing
- Performance, Load, and Stress Testing
- A Comparation of Some Performance Testing Tools
- Performance Measures and Evaluation on IR System
- A communication conference on performance testing
- Recording and Performance testing Android
- Some insights on PDM, ADM and Schedule
- Give some advice on how to learn html,css,and javascript for c developers
- Some Testing on Intra-Block Row Chaining
- Difference between Load / Stress / Performance Testing
- SQL Injection Attacks and Some Tips on How to Prevent Them
- Advanced Unit Testing, Part IV - Fixture Setup/Teardown, Test Repetition And Performance Tests
- Performance Testing vs. Load Testing vs. Stress Testing
- Some insights on PDM, ADM and Schedule
- Performance vs. load vs. stress testing
- Some tips on using HashSet<T> and List<T>
- Temporary Tables vs. Table Variables and Their Effect on SQL Server Performance
- gprof, Valgrind and gperftools - an evaluation of some tools for application level CPU profiling on