18.
Share some of your QA experiences.
I
was involved in the testing of the product that was for a project that had to
support at least 30 items in the input criteria. The quality was measured as
the number supported by the system. The test script was developed to simulate
20 or more input items. The testing on the periodic basis helped the developers
to go in the right track and develop the various aspects of the product without
affecting the number of items supported.
19.
How can you bring about quality changes in adverse environments?
The
quality changes in environments which are very static and not adaptable have to
be done very carefully. Sometimes the quality changes may require change from
the base in adverse environments, so spending good amount of time in designing
the right architecture depending on the environment right from the start is
essential when we are not sure about the adaptive nature of the environment or
user.
20.
Is test automation a required thing at all?
The
tests in many cases are not a single execution of the program and there are
always many cases to be tested. The immense number can be overwhelmingly high
to think of manual testing. So in such a case the automation of testing with
test scripts is the right way and the only possible way to go, considering the
value of resources and man hours. This can be considered the smart way of
working and most often this proves to be effective and efficient.
21.
How can we have a effective phase containment concept incorporated into the
project development cycle?
The
testing should be done in parallel along with development over the various
stages of deliverable. This way the errors are not propagating across the
various phases of the project. This phase containment mechanism can result in
avoiding defects in the final product that is being created. The more
methodical and frequent we have the testing and workable product across the
timeline the more effective the phase containment will be.
22.
What are the various testing mechanisms you have done in your experience?
The
regression, load tests and the module wise testing was done by me in the
previous project that I was involved in. The regression testing gave the exact
errors that were found in the application along with the appropriate test cases
that have failed. The load testing was more of a stability test over the
application and was to prove the quality of the product in terms of performance
and stability to the customer. Both of them were automated and run at various
stages of development.
23.
How will you start with a new project, assuming you are put into a new team
that is embarking on a new development project?
The
first week will be purely dedicated to gaining of knowledge relating to the
various technologies, methodologies used in the project. After this will be the
phase where I will involve myself in getting to know more about the project
that is being developed. The use cases, purpose of the project will be the
start point and the modularity and design architecture will be analyzed by me
and peer reviews and interactions with the team regarding the phases of testing
and development will get me into the project completely. After this the
planning and execution of the test plan will help me ensure the project is
going as expected from every aspect of view.
24.
How will you go about developing a test plan for a project?
That
more often depends on the methodology used. Say, for example if there is RPD
based development the test plan will be more interactive with the development
plan. The modularity of the project, in every methodology has to be brought out
in the test plan, so that the testing can recognize the potential areas of
integration related weaknesses. The test plan also should impose upon the team
members appropriate responsibilities so that each have their own perspective of
delivery clear when it comes to test cases.
25.
How do you expect a Software testing environment to be?
A
Software testing environment should be very adaptable and should be
configurable to simulate any kind of situation for the product under test. The
exhaustiveness of the testing is directly related to the configurable aspect of
the environment.
26.
Do you have any prior experience in writing test cases? How did you proceed
writing them?
Yes,
I do have experience in writing test cases for the testing purposes of the
project. The test cases should have a clear input category and output category.
The inputs should be pertaining to the test’s aim. The output should
automatically be scanned for correctness for deciding the failure/success
demarcation. The test case also conforms to specific requirement from the
client side or atleast a part of it. To ensure the correctness and validity of
the output, we should be having the right idea of the customer expectation.
Once we have the sufficient knowledge in the above aspects, we can have the
best test case with apt goal to satisfy from the customer’s standpoint.
No comments:
Post a Comment