Test .Net Projects

Question

Hi *
Can every one tell me about type of test in a application. I heared obut TestCase, UnitTest, FunctionalTest and another type of test, but I don't know these discription and usage of these. Please help me to understanding all about Test Process in a application.
thanx

Answer 1

Amir,

 

Each organization may have its own custom test process. An organization may have a (documented) test policy that dictates the types of testing e.g. feature/ functional testing, performance testing that would be performed on each application developed within it. Further, each project may have its own test strategy that takes into account the requirements of the project and the organizational test policy.

 

Broadly speaking, the test process is usually aligned to the various phases of the software development life cycle chosen for the project.

 

For example, unit testing takes place along with or following coding, integration testing is aligned with the integration of components. These types of testing are followed by system testing and acceptance testing.

 

The test process should take into account the testing activities that would be performed, test tools that would be used and the bug life cycle. The test process should be designed in such a manner that the testing requirements of the project, the customers and the organization are satisfied using (possibly) the minimum (or reasonable) number of resources (test environments and human efforts). In order to get everyone on the same page, it is prudent to communicate and discuss the test process prior to its execution in the project.

 

When the test process is executed, it is useful to analyze the data gathered on the process. Sometimes, it makes sense to alter the process. Some examples are:

1. A type of bug is identified and this type of bug needs to be handled with a different bug life cycle. The test process is enhanced to include the special bug life cycle.

2. It is observed that the test engineers are spending too much time on some documentation with a not-so-high value. The test process is then altered to reduce or eliminate such documentation.

3. Certain testing activities cause conflicts with some other testing activities. The test process is then altered to sequence these activities one after the other.

4. The test engineers identify certain repeat tasks. It is decided to automate these tasks. The test process is then altered to use the automation.

 

Instead of designing a test process up-front, it is also possible for a project team to begin testing activities using a simple and generic (generic to similar projects) and refine it with each iteration of the test process.

 

Thanks,

Inder P Singh

Blog: Software Testing Space