What is Execution Based Testing and Non Execution Based Testing?

1. Non execution based testing means the module is always reviewed by a team. The non execution based testing relies on fault detection strategy.

The fault-detecting power of these non-execution based testing techniques leads to rapid, thorough, and early fault detection.

Non-execution based testing is also known by the name static testing or you can say by static program analysis.

2. Execution based testing: - On this execution based testing the modules are run against test cases. Following are the two ways of systematically constructing test data to test a module.


Types of Execution Testing

Why do Bugs occur in the software?

Bugs are a mismatch between expected result and actual result. Bugs play an important role in software testing.

In little we can say that bugs can be of diver’s types which could be always effective in software testing. Software bugs pose a great threat to the software industry.


Why Bugs Occur in the Software?

Plentiful studies have been on very little projects to extremely large ones and the analysis shows various causes of bugs in the software, few of them are listed below: -

1. One of the extreme causes is the specification. In several cases, specifications are the largest producer of bugs. Either specifications are not written, specifications are not thorough enough, constantly changing or not communicated well to the development team.

2. Another  bigger reason is that software is always created by human beings. They know numerous things but are not expert and might make mistakes.

3. Further, there are deadlines to deliver the project on time. So increasing pressure and workload conduct in no time to check, compromise on quality and incomplete systems. So this leads to occurrence of Bugs.

Some common types of software bugs

What is Spike Testing Explain it with example?

Spike Testing is a form of testing process in which an application is tested with unusual increment and decrements in the load. The system is unexpectedly loaded and unloaded. It is done to notice how actually the system reacts with unexpected rise and decline of users.

Spike testing example is given below

Considering example when you are always checking the result of your exam on K.U.K site means site is suddenly loaded and unloaded and then the IT squad of K.U.K check how the site reacts with unexpected increase and decrease of users than it is spike testing.

Spike testing is mechanism of testing which means when in a web page frequent number of visitor access the page unexpectedly increases to maximum then obviously performance of the page breaks down. So the mechanism of testing a performance about web page due to unexpected sort of traffic on the page is always called as Spike testing.

Spike testing is usually done by unexpectedly increasing the number of loads generated by users by a very enormous amount and observing the dramatic behavior of the system.

Explain Importance of Testing In SDLC?

Testing is one of the important aspects in SDLC because of the following reasons:

1. Testing in SDLC helps to prove that all the software requirements are always implemented correctly or not.

2. Testing helps in identifying defects and ensuring that testing are addressed before software deployment. If any defect is discover and fixed after deployment, then the correction cost will be much huge than the cost of fixing it at earlier stages of development

3. Testing in SDLC demonstrates that software always appears to be working correspond to specification, and the sociology and performance requirements always appear to have been met.

4. Whenever several systems are developed in different components, different levels of testing help to verify proper integration or interaction of all components to rest of the system.

5. Testing in SDLC means that testing always improves the quality of product and project.

Conclusion:

Testing plays an important role in SDLC and apart from that testing also improves the quality of the product and project by discovering bugs early in the software.

And remember testing not only improves the quality of the product, but it also improves the company quality also.

What do you mean by soak testing?

Soak testing is different type about performance testing in which tester always test the stability and response time of affecting application by request the designed load for a longer time.

Soak testing is sometimes also called as endurance testing and longevity testing.

Soak Testing is the form of Performance Testing, which incorporate testing a system with expressive load extended over an expressive period of time, to discover how the system and product behaves under repeated use.

Example of soak testing:

Considering example in a banking environment large amount of load is expected at the deadline of every month, means on the time of banking closing days.

So tester always perform the soak testing on banking application to test huge levels of load for prolonged amount of time. So in banking application tester put the grand amount of load for prolonged amount of time like put load for 72hrs to 120 hrs, to check how application behaves during this load period.

Soak testing means running a system at huge levels of load for prolonged amount of time. A soak test would generally execute some times more transactions in an entire (full) day (or night) that intend be expected in a busy day, to distinguish any performance issues that appear after a immense number of transactions have been executed.

Write Test Cases of Pen?

Test cases of pen are given below: -

But keep one thing in mind that test cases for pen may vary if you have different requirements or set of requirements.

Below is given different test cases of pen which does not contain any requirements or specifications?

Test cases of pen are like that:

1. Verify the color of the pen.
2. Check GUI testing means logo of the pen maker.
3. Check Usability testing means grip of the pen.
4. Verify whether the pen is ballpoint pen or ink pen.
5. Check Integration Testing means cap of the pen should easily fit beside the body of the pen.
6. Check pen should be continuously in writing mode.

Some Functional test cases for pen:

1. Check whether it writes on paper or not.

2. Verify whether the ink on the paper is belongs with the similar color as what we see in the refill.

Explain Positive Testing And Negative Testing With Example?

Positive Testing: - When tester test the application from positive point of mind than it is known as positive testing.

Testing the application with valid input and data is known as positive testing.

Positive testing: - A test which is designed to check that application is correctly working. Here the aim of tester is to pass affecting application, sometimes it is obviously called as clean testing, and that is “test to pass”.

Negative Testing: - When tester test the application from negative point of mind than it is known as negative testing.

Testing the application always with invalid input and data is known as negative testing.

Example of positive testing is given below:

Write test cases of fan?

There are numerous test cases of fan which are given below:

Test case 1: Check whether it moves or not.

Description: Ensure that fan should moves properly.

Expected result: Fan should be moving.

Test case 2: Check it should have minimum 3 blades.

Description: Ensure that length of fan blades should be considered to 3 blades.

Expected result: Length of fan blades should not be shorter than 3 blades.

Test case 3: Check it should be on when electric button (switch) is on.

Description: Ensure that fan should start working when electric switch is on.

Expected result: Fan should be on when electric button (switch) is on.

Test case 4: Check whether Speed of the fan definitely be controlled by the regulator.

Description: Ensure that speed of fan should be controlled.

Expected result: Fan speed should be controlled by the regulator.

Test case 5: Check it should be stop working once the electric switch off.

Description: Ensure that fan should stop working once the electric switch is off.

Expected result: Fan should be off once electric switch is off.

What is Testing Why It is Necessary?

Testing is necessary to increase the quality of the project. Testing is most time consuming, but a crucial activity of a software project.

It is vital to the success of new system. For making the project reliable and Error Free, the complete project and product must be tested in a systematic and organized way.

DEFINITION OF TESTING

(According To Hetzel)
Testing is the mechanism of establishing sureness that a program or product does what it is supposed to do.”

(According To Glen Meyers)
“Testing is the mechanism of executing a program or product with the intent of finding errors.”


WHY NEED OF TESTING

It is remarkably performed for one of the two reasons: -

1. Bug Detection

2. Improvement belonging to quality

Testing is needed not always for improving product and project quality but also for improving company quality. Without testing company can’t grow at the upper level.

Testing is needed for almost all the organization which wants to grown up easily. Testing is needed for properly understand the fault errors in software during its development phases.

Testing is necessary in software development. It always ensures the users satisfaction and reliability of affecting software.
Related Posts Plugin for WordPress, Blogger...