Disadvantages of Manual Unit Testing

Some of the issues of manual unit testing are: You will write test applications and throw away after doing your testing. After few weeks you may make some modifications to your code and at that time you may not find your old test application. So, you will have to write another test application. Large projects will have hundreds of classes and several class libraries. It is very difficult to write separate test applications for each of the classes in the project and save all of them for repeated testing in future. Test applications require a human person to test. You … Click here to continue…..

What is unit testing?

After writing any code, every programmer will do some kind of testing to make sure the code works as expected. This testing is called ‘unit testing’. Unit testing is done in different ways. Some programmers write simple test applications to test their own code. Some others simply debug the code and change the values during debugging to make sure the code works fine for different cases. Some facts about unit testing: Unit testing is done by developers. Quality department does different tests, they are not unit tests. Every programmer must do unit testing after finishing development or during development itself. … Click here to continue…..

What is configuration management?

Configuration management is a detailed recording and updating information for hardware and software components. When we say components it does not only mean source code. It can be tracking of changes for software documents like requirement, design, test cases etc. When changes are done in ADHOC and uncontrolled manner more chaotic situations arise and more defects are injected. So whenever changes are done it should be done in a controlled fashion and with proper versioning. At any moment of time we should be able to revert back to the old version. The main intension of Configuration management is that we can track our changes back if we … Click here to continue…..

what do you mean by coverage and what are the different types of coverage techniques?

Coverage is a measure used in software testing to describe to the degree to which the source code is tested. There are three basic types of the coverage techniques as shown in the below figure:- Statement coverage: – This coverage ensures that each line of source code has been executed and tested. Decision coverage: – This coverage ensures that every decision (true/ false) in the source code has been executed and tested. Path coverage: – In this coverage we ensure that every possible route through a given part of code is executed and tested. Coverage techniques

Can you explain regression testing and confirmation testing?

Regression testing is meant for regression defects. Regression defects are defects due to which the functionality which was working first normally has stopped working. This is probably because of changes made in the program or the environment. To uncover such kind of defect regression testing is conducted. Below figure shows the clear explanation and difference between regression and confirmation testing. If we fix a defect in an existing application we use confirmation testing to test if the defect is removed. It’s very much possible because of this defect or changes to the application it can affect other sections of the application. So to ensure that no other … Click here to continue…..