Simplifying Concepts

Essence of Life is in Simplicity

Load and Stress Testing

Difference between Load and Stress Testing?
Compare Load and Stress Testing?

Differentiate/Compare/ Difference between Load and Stress Testing.

Load Testing

Stress Testing

Suppose, if an application is built for 500 users, then in load testing we check for up to 500 users.

Suppose, if an application is built for 500 users, then in stress testing we check for greater than 500 users

It helps us to study the behaviour of application under loads.

It helps us to study the breaking point of the system/ server.

It determines the reliability of the application.

It determines the stability of the application.

The parameter under focus is the response time.

The parameter under focus is the throughput.

Load testing is subset of Stress testing.

Stress testing is superset of Load testing.

Load testing is done to ensure that the system meets the specified load. (I.e. whether system has load bearing capacity.)

Stress testing ensures whether the application meets the unexpected loads.

Testing the app with maximum numbers of users and input is load testing.

Testing the app with more than maximum number of users & inputs is stress testing.

Load tests are more formal and usually predefined by client and domain experts.

It is informal and is needed to overcome & understand erroneous situations possible.

It is called operational capacity testing.

It is also sometimes called torture testing.

Load testing could be considered like a non destructive test.

Stress testing is considered like a destructive test.

It involves maximal utilization of resources.

It involves denial or unavailability of resources.


Note: The above differences have been derived through a proper understanding. So please share the link of this webpage as “sharing is a way of spreading knowledge”. But, please do not copy & paste it in other Website or Forums.

Hey guys we are eager to hear from you, about your views and your thoughts. Let us know how much you like the differences mentioned above. Please give your comments and if possible share because “Sharing is Caring”.

Static and Dynamic Testing

Difference between Static and Dynamic Testing?
Compare Static and Dynamic Testing?

Differentiate/Compare/ Difference between Static and Dynamic Testing.

Static Testing

Dynamic Testing

It is testing without executing the software.

It is testing that involves the execution of software.

It can start early in the software lifecycle.

It can start after the development of software component.

Software is examined manually and some static analysis tools are used.

In this by giving inputs, its outputs are examined & compared with what is expected.

Review, inspection and meetings come under static testing.

Unit, Integration, System & acceptance testing come under dynamic testing.

It involves finding bugs before compiling.

It involves finding bugs after compile & linking.

It is about prevention.(Preventing errors from being occuring)

It is about cure.(It allows to figure out errors and fix them)

It is more cost effective.

It is not cost effective.

It is done usually in verification stage.

It is done usually in validation stage.

It guarantees 100% statement coverage.

It does not guarantee complete code coverage.

More reviews and comments (on source code) are highly recommended for good quality software.

More defects (uncover) and its correction is highly recommended for the good quality software.

Missing requirement, design defect and syntax errors are the defects found in this testing.

Variable not constant, functionality missing are kind of defects found in dynamic testing.


Note: The above differences have been derived through a proper understanding. So please share the link of this webpage as “sharing is a way of spreading knowledge”. But, please do not copy & paste it in other Website or Forums.

Hey guys we are eager to hear from you, about your views and your thoughts. Let us know how much you like the differences mentioned above. Please give your comments and if possible share because “Sharing is Caring”.

Unit and Integration Testing

Difference between Unit and Integration Testing?
Compare Unit and Integration Testing?

Differentiate/Compare/ Difference between Unit and Integration Testing.

Unit Testing

Integration Testing

It is a testing method that verifies whether individual units of source code are working properly.

It is a level of testing in which individual software modules are combined and these combined modules are tested.

Thus unit test is done in isolation.

Integration test is done in modules.

Unit testing checks a single component of the application.

It checks if different units work together as an application.

The errors in unit testing are internal in nature.

The errors are by large external in nature.

Usually errors include bugs, syntax errors and logical errors.

Usually errors in integration testing include interfacing errors.

Various approaches/ strategies of unit testing include:
a. Static Unit Testing
b. Dynamic Unit Testing

Various approaches to Integration testing are:
a. Incremental
b. Top-Down approach
c. Bottom-Up approach
d. Sandwich
e. Big bang

Unit test cases are easier to understand and maintain.

Integration test cases are hard and difficult to maintain.

Usually units are built by a single person, so developers are the people who are responsible for unit testing.

Multiple units are built by different people, so testing is carried out by system integration tester.

Unit tested modules never fulfil the final functional requirements.

The outcome of Integration testing fulfils the functional requirements, but yet it requires system validation.

The developer can continue testing till his will or till the time he wants.

Testing continues till the complete combined version of the system with no interface errors is built.

It occurs before integration and system testing.

It occurs or is only possible once the unit testing is done.


Note: The above differences have been derived through a proper understanding. So please share the link of this webpage as “sharing is a way of spreading knowledge”. But, please do not copy & paste it in other Website or Forums.

Hey guys we are eager to hear from you, about your views and your thoughts. Let us know how much you like the differences mentioned above. Please give your comments and if possible share because “Sharing is Caring”.

Alpha and Beta Testing

Difference between Alpha and Beta Testing?
Compare Alpha and Beta Testing?

Differentiate/Compare/Difference between Alpha and Beta Testing.

Alpha Testing

Beta Testing

It is always performed by the developers at software development site.

It is always performed by the customers or users at their own site.

Alpha testing is the first phase of User Acceptance Testing.

Beta testing is the testing usually followed by alpha and is called pre-release testing.

It is usually performed under the directives of independent testing team.

It is usually not done by independent testing teams instead by users themselves.

In this the software release is not open to general public.

In this software is open to the public and possibly have errors hence called beta version.

It is performed inside an organisation.

It is performed outside an organisation.

It comes under the category of both white box and black box testing.

It is a kind of black box testing.

It is conducted in virtual and controlled environment.

It is conducted in real and live environment.

It is conducted when development of software is near to completion stage.

It is conducted before the final launching or releasing of software.

The number of people involved in this testing process is small.

The number of people involved is high as testers themselves are potential users.

In this usually developers record the problems encountered during the process of testing.

In this developers have no role, instead users when face errors they report to the developers.

It is done to ensure that plenty of bugs & missing features as specified in specification are up to the mark.

It is done to ensure that no loopholes or drawbacks exist before the final release of the complete software.

Example: Testing of newly system tested software (It can be any business software).

Example: Initially Bluestacks an android emulator was released to public as bluestacks-beta.


Note: The above differences have been derived through a proper understanding. So please share the link of this webpage as “sharing is a way of spreading knowledge”. But, please do not copy & paste it in other Website or Forums.

Hey guys we are eager to hear from you, about your views and your thoughts. Let us know how much you like the differences mentioned above. Please give your comments and if possible share because “Sharing is Caring”.

Verification and Validation

Difference between Verification and validation?
Compare Verification and Validation?

Differentiate/Compare/Difference between Verification and Validation.

Verification

Validation

Are we building the system right?

Are we building the right system?

Verification involves activities namely reviews, meetings and inspections.

Black box testing, White box testing, grey box are the activities involved in validation.

It is carried out by quality assurance team.

It is carried out especially by testing team.

Execution of code does not come under verification.

Validation involves execution of code.

It is carried out before validation.

It follows the verification.

During verification plans, requirement specification, design, code and test cases are evaluated.

During validation actual product or software under test is evaluated.

Cost of errors (cost of correcting) caught is relatively less compared to validation.

Cost of errors (cost of correcting) caught during validation is relatively high.

It checks whether software conforms to specification.

It checks whether software meets customer expectations & requirements.

It is a low level exercise.

It is a high level exercise.

Verification is the process of evaluating product of a development phase to find out whether they meet specified requirements.

Validation is the process of evaluating software at the end of development process to determine whether software meets customer expectations and requirements.

It ensures that the software system meets all the functionality.

It ensures that the functionalities meet their intended behaviour.

Note: The above differences have been derived through a proper understanding. So please share the link of this webpage as “sharing is a way of spreading knowledge”. But, please do not copy & paste it in other Website or Forums.

Pages:123
error: Content is protected !!