Monday, March 2, 2015

Best Difference between Navigation Testing and Usability Testing

People are aware regarding Usability Testing, but they do not know about Navigation Testing. So here I am writing the Difference between Navigation Testing and Usability Testing both so that those who have confusion in their mind regarding the Navigation and Usability Testing can simply increase their knowledge by seen the difference on both these confusing terms.

             Navigation Testing
              Usability Testing
1. Navigation Testing is done to ensure that external and internal links are working properly.
1. Usability Testing is always done to ensure/verify that the GUI is well designed and easily used.
2. Navigation Testing is more users friendly and it provides ability to navigate from current page and it provides ability to navigate from current page to other pages directly.
2. Usability Testing is always done to verify how much the application is user friendly to an end user.
3. In Navigation Testing, tester use the visual hierarchies like color, position etc.
3. In Usability Testing tester always test whether the control flow of the application is convenient for end user or not.
4. Navigation allows user to control the interaction sequence of pages in the application.
4. In Usability Testing tester always test whether the interaction of functionality with the user is effective in nature or not.

Advantages and Disadvantages of Dynamic Testing

Advantages of Dynamic Testing are many but apart from advantages dynamic testing have some Disadvantages too. So I am writing the post on both Advantages and Disadvantages of Dynamic Testing so that all stuff can be get in one place.

Advantages of Dynamic Testing – Complete

Below is given the Advantages of Dynamic Testing and hope these advantages can clear your doubts more.

1. Considered High Level Exercise: One of the main and most crucial advantages of Dynamic Testing is that it can always find errors that static testing cannot find and that is the reason why it is considered as high level exercise.

2. Improves Quality: Another main advantage of Dynamic Testing is that it improves the quality of software because Dynamic Testing means executing the software and when we execute the software chances are higher for finds many bugs in the application so it ensures error free software to some extent and hence increases the quality of a product and project.

Dynamic Testing Disadvantages

1. Time Consuming: Main disadvantage of Dynamic Testing is that it is always considered as a time consuming task because its aim is to execute the application/software or code and hence as a result more test cases are needed to execute, so obviously executing more test cases can result in waste of time means consume lots of time.

2. Increases cost of Product: Another disadvantage of Dynamic Testing is that it increases the cost of project/product because it is not starting early in the software life cycle and hence bugs fixed in later stages can result in increase of cost.


3. Execution Costly: One of the main and most important disadvantages of Dynamic Testing is that its execution is costly because as you know Dynamic Testing means execution of software so it requires more man power to complete its task and hence resulted in higher cost to perform Dynamic Testing.

Sunday, March 1, 2015

Explain Non Functional Testing With Example

Non Functional Testing is that in which we test the application/software against client’s expectations and performance requirement. In short we can say this testing is always validating the performance of the application example include Load and Stress Testing.

After successfully completing the Functional Testing, the testing squad is always concentrating on Non Functional Testing. During this period of testing, the testing squad is concentrating more on customer expectations or you can say software characteristics.

Non Functional Testing covers both Load and Stress Testing, Performance Testing, Security and Recovery Testing, Scalability Testing, Localization and Installation Testing, Compliance and Compatibility Testing, Data Conversion Testing, Volume Testing, Migration and Operational Readiness Testing and so on.

Non Functional Testing Example

Example of Non Functional Testing is quite similar to “Functional Testing Example” the only difference is that in Non Functional Testing we have to concentrate on client expectations or in short you can say we have to concentrate on Non Functional Parameters.

For example you are testing a website of K.U.K (Kurukshetra University Kurukshetra). Now as you know during the time of K.U.K Result there are many students who access the K.U.K Result website at the same amount of time. So the owner of K.U.K wants the proper Non Functional Testing on their website. In short you can say that owner of K.U.K wants the proper Non Functional Testing parameters like Endurance Testing, Compatibility Testing, Localization Testing, Compliance Testing, Usability Testing, Scalability Testing, Volume Testing, Load Testing, Performance Testing, Stress Testing, Security Testing, Recovery Testing etc.

Keep one thing in mind that owner of K.U.K give more emphasis on Load, Stress, Usability, Security, and Recovery Testing. As you know it is the Result website so Security and Recovery Testing is must, but apart from Security and Recovery Testing load and stress testing is also very essential because during the time of Result load definitely increases and chances are higher for getting the position of Stress also.

Conclusion

At end we conclude that Non Functional Testing is always concentrating on client/customer expectations and Functional Testing is always concentrating on client/customer requirements. You can also give your valuable suggestions and feedbacks for further improving the very interesting post.

Saturday, February 28, 2015

Difference between Smoke and Regression Testing in Tabular Form

Distinction between Smoke and Regression Testing - Simple

              Smoke testing
               Regression testing
1. Smoke testing is a surface level testing to verify/ensure that build provided/given by development team to QA team is ready to accept for further testing.
1. Regression testing is not considered as a surface level testing and it is performed/ executed by testers only.
2. Smoke testing is known as a quick-and-dirty test means that the major/crucial functions of a piece of software work/perform without bothering with finer details.
2. Regression testing is not known by the quick-and-dirty test and in this testing testers test the application with more details.
3. It is executed/ performed when testers have to accept a build for further testing.
3. It is executed/performed when tester’s have enough time for testing.
4. Smoke testing may be conducted manually or by using automation tools.
4. Regression testing is also conducted manually or using automated tools.
5. Performing smoke testing will not enlarge the product cost and budget because it didn’t requires more manpower and time.
5. Performing Regression testing definitely will enlarge the product cost and budget because it requires more manpower and time.
6. It is also called as BAT (Build Acceptance Test) or BVT (Build Verification Testing).
6. It is not known by any other name.
7. It is done by developers before the build is released or by testers before accepting a build for further testing.
7. It is usually done by testers only.
8. We use script for smoke testing.
8. We use script for regression testing.


Exact Difference between Adhoc and Exploratory Testing

Difference between Adhoc and Exploratory Testing

           Adhoc Testing
            Exploratory Testing
1. Adhoc Testing means learn the application than test it.
1. Exploratory Testing means test the application while learning.
2. In Exploratory Testing QA is always asked to test an application without any specific set of documents.
2. In Adhoc Testing QA is always asked to test an application with detailed set of documents.
3. In this Testing we always gather information regarding the software/application from complete possible sources and document and then test the application/software.
3. In this Testing we gather the information, and also document and test the application simultaneously.
4. In Adhoc Testing tester should have good knowledge about the application in order to test the software.
4. In Exploratory Testing tester should increases their knowledge by exploring the application/software.
5. In this testing testers have significant testing of the software before test it.
5. In this testing testers may be learning the software before testing it.
6. It is not considered as a type of any.
6. It is considered as a type of Adhoc Testing
7. It is not an approach to testing.
7. It is an approach, not a technique.


Friday, February 27, 2015

Complete Difference between Functional and Non Functional Testing

Before us proceeding towards the Difference between Functional and Non Functional Testing it is very important for us to first take a brief look at Functional and Non Functional Testing.

Functional and Non Functional Testing is what?

Functional testing is performed using the functional specifications provided by the client or you can say by using the design specifications like use cases provided by the design team.

In this, tester has to test the application to see that all requirements of the client which he has said in SRS or BRS have been incorporated or not.
Non Functional Testing is that which is always concerned with the client expectations like performance, load and stress issues and so on.
Distinction between Functional and Non Functional Testing

                  Functional Testing
               Non- Functional Testing
1. In functional Testing tester tests how well the system performs.
1. In Non-Functional Testing tester tests how well the system responds.
2. Functional Testing is based on client requirements.
2. Non- Functional Testing is based on client expectations.
3. Functional Testing means Testing the application against business requirements.
3. Non- Functional Testing means Testing the application against clients and performance requirements.
4. It is a part of System Testing.
4. It is also a part of System Testing
5. Functional Testing Validating the behavior of application.
5. Non- Functional Testing Validating the performance of application.
6. This Testing covers Unit Testing, Integration Testing, Smoke Testing, Sanity Testing, Regression Testing and so on.
6. This Testing covers Load/Performance Testing, Stress/Volume Testing, Security Testing, Installation Testing and so on.
7. It is always concentrating on customer requirements.
7. It is always concentrating on customer expectations.
8. Functional Testing means how is your system is doing.
8. Non- Functional Testing means how well your system is doing example usability, performance and stress testing.


Complete Difference between Sanity and Regression Testing

Distinction between Sanity and Regression Testing

                Sanity Testing
             Regression Testing
1. Sanity testing is a surface level testing where QA engineer verifies that all the menus, functions and commands available/presented in the product are working fine.
1. Regression testing is not a surface level testing.
2. Sanity testing is considered as a subset of regression testing.
2. Regression testing is not considered as a subset of any.
3. This testing is performed/executed when testers have not much/enough time for doing testing.
3. This testing is performed/executed when tester’s have enough time for testing.
4. Sanity testing is usually conducted manually not by using any automation tools.
4. Regression testing may be conducted/consider manually or using automated tools.
5. Performing this type of testing will not enlarge the product/project cost and budget because it didn't require much manpower and time.
5. Performing this type of testing definitely will enlarge the product cost and budget because it requires more manpower and time.
6. Not complete test cases are executed/ performed in the product during sanity testing.
6. During this testing complete test cases are executed/ performed in the product.
7. During this testing tester test the application or product with finer details.
7. During this testing tester test the application or product with more details.
8. We do not use script for sanity testing.
8. We use script for regression testing.

Conclusion

At end we conclude that these are the quick and simple Differences between Sanity and Regression Testing in tabular form but the main difference is in its use. We use Regression Testing when we have enough time for Testing, and we use Sanity Testing when we do not have enough time for Testing.

But keep one thing in mind that purpose of both the Regression and Sanity Testing is same; the only difference is in its use.