Call Us: +91- 8885560202 (India)

+1-707-666-8949 (USA)
Mail Us: Info@VirtualNuggets.com

Define Testing?
1.Testing Means :
The process of evaluated a system or system components by manual or automated means to
verify that its fulfill the specific requirements or to identify difference between expected and
actual results.
(OR)
Testing is the process of executing a program with the intent of finding bugs.

2.Importance of Testing?
Validate and verfiy the program and to get the best Output.

3.Software Testing principles?

Software testing is an creative and intellectually challenging task. When testing follows the
principles given below, the creative element of testing design and execution rivals any of the
preceding software development steps.
Testing done by an independent party:
Testing should not be performed by the person or team that developed the software since they
tend to defend the rectify of the program. The developer is driven by delivery and he will try to
execute the testing as early as possible. The developer is knowledge in testing his codeing and
has a soft corner for his code. The independent tester is driven by quality and will try to break the
code. Hence testing should be execute by an independent person.
Assigning best personnel to the task:

Because testing requires high creative and responsible only the best personnel must be assigned
to designing, implementing, and analyzing test cases, test data and test results. Also note that
from point 1, the testing is being done by an independent tester, the system is new to him and he
has to understand the entire system to test it. It is possible to find errors and issues with software
only when you know the system thoroughly.
Testing should not be planned under the assumption that no bugs will be found:
Testing is the process of executing a program with the finding errors. Good testing will find
bugs and testing is never complete, it is infinite. There should be no assumption that the
software has no errors. Such an assumption would leave tremendous amount of holes in the
system.
Testing should be invalid and unexpected input conditions as well as valid conditions:
The program should generate correct output results when a valid input is given, this is called as
positive testing; Also the software should given correct error messages when an invalid test this
is called as negative testing. We need to given a different range of inputs with varying sets of
values. For example, if the input field is taking a positive integer, we should try with all sorts of
integers, positive, negative, zero, large positive, large negative etc. Also we should try giving a
character, string etc and the expected the correct error message.
The probability of the existence of more bugs in a module or group of modules is directly
proportional to the number of errors already found.If you find a bug in a particular module, the
developers just tend to resolve that error and close the bug. But there is a more chances that there
will be more errors in that program.You need to analyze the issues, why that particular bug is
present and look for common issues in that module, you are going to solve many issues.
Using software static during testing:
The program must not be modify during the implementation of the set of designed test cases.
Modify the program while the testing has started will leave a lot of loopoles in the testing; you
would have finished testing module A and started testing on module B, but by that time, module
A would have changed and the changes are not tested!!!
Document testing cases and test results:
This is very important for Software testers, you need to document the test cases, which can be
used for later testing, may be for the next release. The test results should be documented so that
they can used for analyze if required at a later stage.
Provide expected test results:
A necessary part of test documentation is the specification of expected results, even if provide
such results is impractical. Using the expected results you can verify the software which is under
test and declare whether the software meets the expectations or not.

4.Test Case Format?

Test Case format:
Test Case ID.
Subjective.
Prerequisite.
Scenario.
Expected Results
Illustrate:
Subjective/ Title:
User can create a new community successfully.
prerequisite:
user has to log in to the system
Scenario:
Navigate to Create New Community portlet.
Fill in all the Manidatory fields.
Press Create Community
Expected Results :
Community is created successfully

5.Explain Test Method and TEST Report ?

Test Procedure:
Collection of test scripts.
An integral part of each test script is the expected results.

The Test Procedure document should contain an unexecuted, clean copy of every test so that the
tests may be more easily reused.
Test Report :
Completed copy of each test script with evidence that it was executed (i.e., dated with the
signature of the person who ran the test).
Copy of each SPR showing resolution.
List of open or unresolved SPRs.
Identification of SPRs found in each baseline along with total number of SPRs in each baseline.
Regression tests executed for each software baseline.