As a tester this question is my personal experience
interviewer asked from me that do you feel software
tester should be from high qualification background.

And definitely I just little surprised to
hear that this pattern of questions can also be asked by interviewer because as
a professional means software tester
I never heard regarding this form of questions before.

On that time me just smiled and simply say no Sir I
do not think software tester should
be from high qualification background.

He softly smiled and replied to my answer that why and how
you think so and simply say I believe that software
tester should be from high qualification background.

Then again he replied this means according to your
concern my answer is completely wrong what you say.

Bug
is a mismatch between expected result and actual result. Hope as a
tester you know regarding expected result and actual result.

As a tester whether you are working in small companies or in top MNC, when you detect the bug you have to report it.

But the pattern for reporting the bug differs from companies to companies
like in top MNC’s tester’s always reporting the bug through bug reporting tools.

So various Open Source bug reporting tool available today but popular one is Bugzilla and
Mantis, but Mantis is easier and user friendly than Bugzilla.

As people always knows that there are 1-2 testers in
small companies so in these companies testers never report the bug
through bug reporting tools. Testers
just orally talk it to the development team that in this module we catch
the bug so fixed it.

And similar thing happens it to the developers squad
when they fixed the bug they just call the tester to his and her seat and
said that check whether bug is fixed or not.

But you know this is not the appropriate or right
way to communicate because we are working in a professional environment so we have to follow little documentation also.

Bottom
up strategy just as the name itself clears, is
the opposite of powerful top down strategy. This sort of mechanism
starts with building and testing the modules first which are obviously comes
under the category of low level, than definitely proceeding towards
the working its way ups the hierarchy.

BOTTOM
UP STRATEGY BENEFITS

The
advantages of bottom up integration are like that:

1. There is never urgency or hurry for any kind of program
stubs as we always start developing and testing with the definite or absolute modules.

2. Always Starting at the bottom of the
hierarchy again means that the critical modules are generally built and tested first and
therefore any errors or mistakes in these forms of modules are find out early in the
process.