g.ramakrishna rao

• Jan 9th, 2007

 

hi,

1.           if u r a functional tester the ans is block box testing

2.explain abot any sdlc proces and stlc proces

3. test statargy is a company level doc,developed by pm,which contains test methodology,test guidelines,approch , frame work,process,and etc...

4. test plan is a project level doc,developed by TL main elements are testing boundries,team formation,effort estimation with regard to time,budgect,resources,collecting test deta,collecting possible risks and solutions,

wht to test---- list of functionalities,

when to test ----  scheduling

how to test  --- approch or frame work

who to test ---- responcibilities of each member of testing team

cindrela

 Profile Answers by cindrela Questions by cindrela

• Jan 10th, 2007

 

Differntiate between Waterfall Model and Vmodel

Waterfall Model consist

1.REquirement Specification

2.System and Software Design

3.Implementation and Unit Testing

4.Integration and System Testing

Operation and Mainatencae

In the v model Testing i s not at end but done parallely

Businnes Requirements ------------------------------------User Acceptance Testing

     System Design----------------------------------------System Testing

         Detailed Desing -----------------------------Integraton testing

                  Code-----------------------------Uniit testing

          Its in a V shape

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 9th, 2009

 

1) What type of testing do testers normally do?
Most testers perform functional (or black box) testing.

2) What software development processes do company's employ?
We use Waterfall.  Some other options are CMM, RUP, V-model, Agile, and Extreme.

3) What is the meaning of test strategy?
It is a plan that guides test design and execution. 

4) What are key components of a Test Plan document?
a) Introduction
- Purpose
- Product description
- System architecture
b) Scope
- Test coverage
- Features to be tested (in scope)
- Features not to be tested (out of scope)
- Compatibility matrix
- Assumptions
- Risks
c) Approach
- Test objectives
- Test strategies
- Test environment
- System dependencies
- Test tools
d) Process
- Test process and guidelines
- Priority and Severity defined
- Pass/fail criteria
- Test entry/exit criteria
- Test resources
- Deliverables required for testing
- Roles and responsibilities
- Approvals and sign off

5) What is the difference between test strategy and test plan?
- A test strategy describes the general approach to testing in terms of people, tools, procedures and support. 
- A Test plan is a document that describes the scope, approach, resources, and schedule of intended testing activities.
- A test plan often includes the organization's test strategies.

6) How do testers select reasonable tests to be applied in test projects?
By reviewing and understanding the 1) functional requirements and 2) technical specifications.

7) What methods are generally followed to prepare test cases?
- Study and learn about requirements and specfications
- Ask questions to fill gaps in knowledge
- Create test cases
- Map requirements to test cases
- Prioritize test cases
- Conduct peer review of test cases

8) What is a typical test case format?
- Test case id
- Priority
- Severity
- Requirement id
- Tester name
- Created date
- Last updated
- Reviewed date
- Reviewed by
- Target build
- Defect reference number
- Execution date
- Test status (Pass; Fail)
- Title
- Objective
- Prerequisite(s); Precondition(s)
- Environment
- Test steps
- Expected result
- Actual result
- Comments
- Supporting document(s)

9) How many levels of test execution are there?
The number of test iterations (test cycles) depends on a) the complexity of the application under test, b) the resources allocated to test it, and c) the time allotted for testing. Though I estimate the number of test cycles, it all comes down to whether or not the application has met our exit criteria.  Compromises are sometimes made when business stakeholders insist they can "live with" the current state of the application.

10) What is the difference between planned test execution and ad-hoc test

execution?
- Planned test execution is the formal and structured process of running manual test cases or automated test scripts.  
- Ad-hoc test execution is the informal and unstructured process of testing with without test cases.  It attempts to take advantage of a tester's intuition and imagination.

11) How is severity and priority determined?
- Severity is the measure of a defect's impact on a user.
- Priority is the measure of urgency attached to fixing a defect.
- We set levels of Severity and Priority on each defect to identify which defects are most important to fix in the current release of the product.
- Testers choose proper Severity and Priority levels by using good judgment, common sense, and through experience.

12) How do testers report defects to development teams?
Through a distributed defect management system that is shared by testers and developers. I have used Product Studio, Quality Center, and other systems for this purpose.

13) How do testers know whether their reported defects are accepted or rejected?
Testers report defects, the default status is always set to 'Open'.  After developers take action on the defects, they will revise the defect status to correspond with the outcome of their investigations and actions.  When developers accept the defect, they will return defects back to testers with statuses labeled 'fixed' or 'postposed'.  When developers don't accept defects, they return defects with statuses labeled 'by design' or 'not repro'. Of course, the labels may vary between companies, but the process is generally the same.

14) What is defect aging?
Defect aging represents the duration of time between defect identification (when it was first reported) and closure (when no more effort will be applied to it).  Test Management will conduct defect aging analysis to detemine how well their test processes are going.

15) What should testers do when their reported defects are rejected?
- First understand the reason(s) for rejection and determine whether they are valid. 
- If not valid, then offer compelling evidence which proves the defect is real and should be fixed. Do this by a) more fully describing the environment in which the defect was found, b) augmenting your case with excerpts from credible supporting documentation such as functional requirements, or c) adding visual snapshots of the defect.
- If developers still resist, meet with them and include other expert stakeholders and try to reach an understanding and consensus as a team.

16) What is the difference between the Waterfall and V-model of software development? 
- The waterfall model is a sequential software development process in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design (validation), Construction, Testing and Maintenance.
- The V-Model is a development process in which progress flows down from Concept, Requirements, and Design to Implementation and then back up again from Integration, System Test, and Operations & Maintenance.

17) What testing should be done when there is no sufficient time?
- High priority tests should be performed first.
- Depending on the time constriction, it may be necessary to abandon low priority tests and engage in ad-hoc tests instead.
- It should be made clear to all relevant stakeholders that the test team will not sign off on the quality of the product without fully testing the product and verifying it meets the company's established exit critera.

18) What testing should be performed when there is no proper documentation?
- The answer to this question depends on the project. The greater the value it is to the company, the more QA should demand requirements.
- Exploratory testing would be performed if there is a need to develop test cases while conducting initial tests.
- Ad-hoc testing would be performed if there was no need to produce test cases for future testing.

19) What is the difference between buddy testing and pair testing?
There are many interpretations of these concepts.  In my opinion, the difference is:
- Buddy testing occurs when one person tests something and another person tests that same thing afterward. 
- Pair testing occurs when two persons test the same thing together. 

20) What are typical challenges that are encountered throughout a testing process?
- Requirements may be ambiguous and difficult to understand.
- Complexity of the application requires more resources than budget allows.
- Test procedures are not followed by team members.
- Testing may require knowledge of technologies that team members are not familiar with.
- Stakeholders and/or client may not be completely aware of the software development cycle and test management may not receive their full cooperation for deliverables.
- Documentation that the test team relies upon to perform test activities may not be regularly updated, are difficult to locate, or do not exist.
- Functional groups that work directly with the test team may slip their milestones which may cause the test window to become constricted.
- The application doesn't meet exit criteria by target deadline and the business sector is forced to make some tough decisions.