December 25, 2011

Unit Testing

The Objective of the Unit testing is to ensure the steps to be followed to confirm that it meets the functional requirements as specified in Program Specifications.
This procedure covers:
  • Testing of the user interface to ensure that information properly flows into and out of the program unit under testing.
  • Examine the local data structure to ensure that data stored temporarily maintains its integrity during all steps in Test Case execution.
  • Test boundary conditions to ensure that the program operates properly at boundaries established to limit or restrict processing.

Test Case Creation

     Test cases are designed using test techniques as identified in test strategy. Test cases should be designed by stepwise elaboration of test condition. Test design includes identification of preconditions, test data requirement, expected result and post conditions.

Each test case should be:


-> Repeatable
-> Verifiable
-> Traceable back to requirement

The test cases mostly designed; can be best executed in manual testing process. Test cases are designed in different ways to make them automation friendly.

Thanks. 

December 21, 2011

How to report a defect having no test case in SIT?

Hi Friends,

Sometimes during testing or I will say during execution of an existing SIT, it happens that a tester get a defect for which no test cases is mentioned in SIT. Then what we tester should do? Tester should not report the bug or should report it?

Let me clarify these questions. Tester should report every bug he/she get during testing. Tester should clearly mentioned the 'Steps to Reproduce' the bug in his bug report. Tester should update the SIT also. One more clarification, quality of a software is not the tester responsibility only, any member of team who get any bug, should report it. There should be be zero UAT bug or atleast we should report the bug before client report it.

Enjoy Software Testing :)

December 17, 2011

Software Test Design

Software Test design

Once the test plan for a level of testing has been written, the next stage is to specify a set of test cases for each item to be tested at that level. A number of test cases will be identified for each item to be tested at each level of testing.

Each test case will specify how the implementation of a particular requirement or design is to be tested, what will be the environment, what will be the steps and the criteria for success of each test.

Unit test specification will detail the test cases for testing individual units of the software.

Integration test specification will detail the test cases for each stage of integration of tested software components. Primary focus is on data flow between the independent units.

System test specification will detail the test cases of system testing of the software. In this design tester try to mimic the real user environment.

Acceptance test specification will detail the test cases for acceptance of the software.Here the actual users test the software in their environment, where software have to actually work.

Enjoy Software Testing :)

December 14, 2011

When you start software testing, remember ...

1) All tests should be traceable to requirements.
Use requirement traceability matrix to trace test cases which you need to execute when do testing. It will give you confidence that all requirements have been covered.

2) Remember pareto principle – 80% defects are in 20% code.
So, drill down the module/page/feature more and more, where you found even a single bug. Don't stop testing after finding a bug, but test that module/page/feature more and more.

3) Testing should be done with incremental approach (unit ->integration ->system)

Unit testing -> Developers
Integration -> Both
System -> Testers

December 10, 2011

What about bugs found in application post delivery at developer/tester end?

Hi Friends,

How are you? It's long time when I am posting this post. Sorry for that actually I was very active on internet due to time constraints. Here I am again with one more experience. Why experience, because I always try to post only that material on my blog which actually I have faced.

I am sure if if any you have worked on a project, where you replaced an existing tester, you have faced this question in your mind, "What about bugs found in application post delivery at developer/tester end?". Definitely this situation sometimes becomes debate, what to do with such bugs.

1) Developer answer will be that the build was tested by tester and it's working fine on live. Client have not reported any issue. So, nothing will be fixed.

2) Tester will force to fix it, because if this issue will be caught by client later any time, he will not blame the tester who have tested it, but to the tester, who is currently testing it.

What I can say, we should talk to team lead for same and at-least should note down the issue as existing known issue and should send the fix to client when developer get chance to work on it. If issue is critical, we should fix the issue and send the build to client telling him the criticality of issue.What you suggests friends, please reply.

Thanks.

Search Here...

Popular Posts

Quick Test Professional