Yes some major companies are following STLC along with SDLC.

But small companies are not

following any of the methods and life cycles.
What we are following in my company is:
1. First will prepare FRS document
2. After FRS will prepare MRD
3. MRD will go for review and finalize final MRD document.
4. Design people will prepare Mockups according to MRD
5. Prepare Test Plan according to MRD & FRS documents
6. Test Plan will send for review.
7. Based on the test plan will prepare test cases
8. Test Cases will send for review
9. Mean while development people we make the feature ready.
10. Some time we will involve in Unit testing also.
11. We will start Integration Testing, Functional Testing, Regression Testing, Re- Testing, System
Testing and finally User acceptance testing also.
Ques
Tell me what you have done in your last project.
> 2.Tell me on what technologies you worked.
> 3.what was your role in the project.
> 4.what was the size of your team.
> 5.how many testcase you write in a day.
> 6.what type of testcase you write.
> 7.what will you do when the build is released and you find defects in
> the build.
> 8. what will you do if you do not have any regression suit .
> 9.How many defects you will find in a day.
> 10.How do you report defects in your project.
> 11.Did you do any backhand testing in your project.
> 12.what backhand testing you did .
> 13.what are the queries you have used in your project.
> 14.Are you willing to relocate.
> 15.Do you have any questions for us
> 16.will you do adhoc testing for all the modules.
Informal Review
o No formal process
o May take the form of pair programming or a technical lead reviewing designs and code
o Results may be documented
o Varies in usefulness depending on the reviewers
o Main purpose: inexpensive way to get some benefit

Walkthrough

o Meeting led by author

o May take the form of scenarios, dry runs, peer group participation
o Open-ended sessions
Optional pre-meeting preparation of reviewers
Optional preparation of a review report including list of findings
o Optional scribe (who is not the author)
o May vary in practice from quite informal to very formal
o Main purposes: learning, gaining understanding, finding defects

Technical Review
o Documented, defined defect-detection process that includes peers and technical experts
with
optional management participation
o May be performed as a peer review without management participation
o Ideally led by trained moderator (not the author)
o Pre-meeting preparation by reviewers
o Optional use of checklists
o Preparation of a review report which includes the list of findings, the verdict whether the
software product meets its requirements and, where appropriate, recommendations related to
findings
o May vary in practice from quite informal to very formal
o Main purposes: discussing, making decisions, evaluating alternatives, finding defects, solving
technical problems and checking conformance to specifications, plans, regulations, and
standards

Inspection
o Led by trained moderator (not the author)
o Usually conducted as a peer examination

o Defined roles
o Includes metrics gathering
o Formal process based on rules and checklists
o Specified entry and exit criteria for acceptance of the software product
o Pre-meeting preparation
o Inspection report including list of findings
o Formal follow-up process
Optional process improvement components
o Optional reader
o Main purpose: finding defects

Walkthroughs, technical reviews and inspections can be performed within a peer group,i.e.
colleagues at the same organizational level. This type of review is called a peer review.
In N-tire Architecture,
Client Side Validation means,
Some of the Inputs of the User will be validated in there systems itself using certain Client side
scripting concept.
Server Side Validation means,
The user inputs will be transferred to Server and in server side it is validated and corresponding
action taken according to that..
Example:
Gmail Login;
Client Side Validation
when u enter wrong email id format, like Gmail id with,
1) _ Character
2) first and last character is not a-z, A-Z and 0-9
3) password length is less then 6
this things are validated in client system i.e. on IE browser itself using Client side scripting
concept.
Server Side Validation
Entered User name and password will be transferred to Gmail server and in server that will be
authenticated... using server side scripting...

Build: Executable version of code.

Patch: Code which is applied on a Build, when an issue or change is encountered
Fix: Code which is developed to fix an issue found is most often for a single issue.
Pilot: Is the jargon for IMPLEMENTATION phase in Waterfall model. For testers it is UAT at client
specified environment.
If Its Web Application :-- Then You may have four different Servers . they are :1) Development Server for Developers ..
2) Test Servers for Testers .
3) Staging Server for UAT.
4) Production Server for Live Use...

the process in various organizations

1) Collect and analyse requirements ( BRS, SRS, URS, TRS, CRS). or using Adhoc/
Exploratory methodology
2) Analyse the Solution Architecture of the system using HLD, SAD, LLD or Use cases.
3) Analyse the wired frames along with design specifications
4) Identify the functional points of the system
5) Identify Test Conditions based or associated with functional point/points.
6) Prepare Test Scenarios based on the Test Conditions.
7) Prepare Test Data using requirements specifications, preferably BRS.1
8) Author test cases based on the template from QMS/SPEG
9) Desk Check, peer reviews and then Inspections to be followed over Test Cases
drafted.
10) Baseline the TC document and ship over to client/client site team for Approval.
I don't know how Test Cases are authored in different organizations.

TM is bi-directional by default; there is no Uni-Directional TM.

1) Forward Trace: which maps the requirements to Defects
2) Backward Trace: which maps the defects to requirements?

as a Software Test Engineer since 3 years 3 months.

I am primarily a Manual Test Engineer with automation knowledge
i.e. QTP 8.2

I am involved in Performing
Usability Testing,
Functional Testing,
Black Box Testing,
Regression Testing,
Re-Testing,
Positive and Negative Testing.(add if anything
more anything more)
My primary job profile is Authoring Test Cases according to the
Client Requirements, Executing Test Cases, Tracking and
Reporting Issues.
I am involved in updating Requirements Traceability Matrix.
I have knowledge of SQL, C, C++ and Java languages.
I am skilled in Manual Testing.
I am involved in updating Daily Status Reports and Weekly Status
Reports.
I have ensured issues resolve by coordinating with Development
team.
I am an active participant in Team Meetings.
I have used bug tracking tool called Change ware.

(2) Tell me about your Project?

What is the Project?

Why this Project?

What is the use of the Project?
Issues encountered and challenges faced during project
life cycle?
What is your contribution towards the Project?
What are the Important Features of the Project?

(3) Tell me about your Organization Testing Process?

Our Techno Marketing team gets the Project.

Testing Process at my current Organization kick starts after the
Requirements are baseline.
BRS is drafted and preparation of UAT Test cases occurs.
After BRS is baseline, our System Analyst prepares the SRS and we
design System Test Cases based on Requirements Specifications.
RTM is prepared go as to confirm the test status.
Based on Requirements our Design Team designs the Design
Specifications, where we design Integration Test Cases.
As we are done with the Integration Test Cases designing our
development team performs Unit Test case design and execution.
Build is delivered to us for execution of the designed Test cases.
We Execute the Test cases and raise Issues encountered and
report the issues to the development team which is a continuous
process.
We perform Regression Testing for each released Build; generally
we perform 4-5 regressions.

Our Project will be signed off after UAT Test Cases are executed &
Customer acceptance.

(4) What are you looking for a change?

I am a man who believes in growing, I believe in learning and
updating my self, as the organisation (positively about the
organization) provides rich learning environment I am looking
forward to join.
I am done with my 3 year contract/comittment with my previous
organization.
I want to learn Load Runner and willing to prosper my career in
Performance testing.(anything such)

(5) Where do you see yourself after 5 years?

I am a planned and organized person, my first goal is to clear the

interview process and give best of my efforts to the organization.
I am planning for Certification (CSQA) this year, so willing to
upgrade myself to QA.
After two years I see my self as a QA Lead, and after 5 years you
can expect me as a QA manager.

(6) Why should I hire you?

I am skilled with good Manual testing experience, with an initiate

to specialized areas such a Performance testing and Software
security testing.

I am a Hard Working person, apart from my job I teach Software

testing every day to my friends.
I am a self learner; I have learnt software Security testing on my
own.
I am work dedicated person, who try to give my 100% efforts at
the end of the day.
I can easily upgrade myself to Automation Tools as I am good with
Programming.

(7) What are your achievements?

Till now becoming a Software Engineer is my greatest

achievement.
Also I have proved myself as able Employee, Son, Brother and
Friend.
Apart from this during my school and college days I captained my
side to victory in Cricket and Football.
I have won Microsoft best question award in Jan-2006 in an online
web cast.

?????? Not getting.

(8) What are your Strengths and Weakness?

Strengths:
My Technical skills are my greatest strength.

I am a Hard Working person, apart from my job I teach Software

testing every day to my friends.
I am a self learner; I have learnt software Security testing on my
own.
I am work dedicated person, who try to give my 100% efforts at
the end of the day.
Weakness:
I question a lot that sometimes may irritate and
anger people, so I prioritize my questions and ask only with the
top priority, trying to overcome the questioning habit.
I have the curiosity to know things completely;
despite of knowing I try to know still further, which I am
postponing to next time to make myself an ever learning person.
I am a straight forward person, so try to control
my talk, as Words once spoken cant be taken back.

Web Servers are basically used to Host Websites and they can also be used for data storage . on
a Web Server we basically perform Non-functional testing . for example :-- Load , Stress ,
Performance and if we Test for data storage that means we would do Volume testing.. etc... So
Web Servers are usually tested with Automation tools... Manually they can't be tested.. The
most common behaviour of a Web Server is to Accept requests from Web clients ( Browsers )
and processing the requests and give the Response back.. so most of the times Load ,
Performance and Stress is tested....

Testing the application from starting to end(Complete Transaction) by validating the internal
and external interfaces is End-End testing.

Definition - What does End-to-End Test mean?

End-to-end testing is a methodology used to test whether the flow of an application is
performing as designed from start to finish. The purpose of carrying out end-to-end tests is to

identify system dependencies and to ensure that the right information is passed between
various system components and systems.
Techopedia explains End-to-End Test
End-to-end testing involves ensuring that that integrated components of an application
function as expected. The entire application is tested in a real-world scenario such as
communicating with the database, network, hardware and other applications.
For example, a simplified end-to-end testing of an email application might involve logging in
to the application, getting into the inbox, opening and closing the mail box, composing,
forwarding or replying to email, checking in the sent items and logging out of the application.