Answer / amulyaranjan behera

5.YES Definitely we need testing for the project in order to
produce a quality product.

6.Code Walkthrough:A Code Walkthrough is where the "author"
of the document or code is walking the "inspectors" through
the code in one meeting. In my company, this method works
better with requirement documents than code.

Code Review:A Code Inpsection/Code Review is where the
"inspectors" get a copy of the code before hand and looks
for issues. After a certain period has been meet for them to
have reviewed the code such as a week then they gather for a
meeting. Depending upon how structured the meeting is
depends upon if it is a code Inspection or Review.
and the testing is start from from five phase.


7.verification is a process to check whether the project is
developing in a right way or not.it is done during the
development process. where as validation is a process to
check whether the developing product is working fine or
not.it is done after the development process.

8. Adhoc testing is testing where testing engineer test the
application in his own style after under standing the all
requirements.

9.Tracebility matrix nothing but it is relationship between
testcases and requirements.In this actual mistake/fault are
identified by traceback or mapping between requiremet-
testcaseid-failed testcase,frs-testcaseid-failed
testcase,srs-testcaseid-failed testcase etc.

10. The baseline document is a document which is once final
then after no data is added further in this document.if some
new changes are made in application there is no chance to
add these data in baseline document.

11. Test life cycle is testing process which is involve in
testing the application in order to produce a quality
product. it contains 6 phases.

Test planning
Test Development
Test Execution
Result Analysis
Bug Tracking Or Defect tracking
Reporting Phase.

12.Regression testing is testing where already testing
functionality is tested again in two senarious.

first Whenever a defect identified by the testing engineer
and rectify by the developer and send it to the testing
department, the testing engineer is first check the defect
functionality and its related functionality.

Second whenever new changes are incorporated by the
developer and send it to the testing department, the testing
engineer is check the old related functionality in order to
sure that these functionality are same or not.

Retesting is a testing where already tested functionality
are tested again with multiple sets of data in order to
check whether application is working fine or not.

13. Bug life cycle is a process in which defects are
identified,isolated and maintained. it contains seven
status.
New,Reopen,Close,fixed for verification,hold,As per
design,Testers error.

14.Bug is nothing but it is a fault in a programme or
Application.

15.If software misses some feature or function from what is
there in requirement it is called as defect.

16. Functional testing is a testing where one performs
testing on an application whenever it is being executed.
And
System testing is a testing where one performs testing on an
application after deploying it to the environment in order
to check whether its working fine or not and also its
stability.

20.Defects are given a priority and severity level. Such
classification is absolutely needed as the development team
cannot resolve all defects simultaneously. The test team
needs to indicate how soon they want to get the defect
fixed, and how big the impact on the functionality of the
application under test is. Let's have a look at the
classification levels:

Defect priority

High: Fix the defect immediately. A core functionality fails
or test execution is completely blocked.
Medium: Fix the defect soon. An important functionality
fails but we don't need to test it right away and we have a
workaround.
Low: Don't fix this defect before the high and medium
defects are fixed but don't forget this defect.

Defect priority indicates the impact on the test team or
test planning. If the defect blocks or greatly slows down
test execution, you might want to select the highest grade
for the defect priority.

Defect severity

Critical: A core functionality returns completely invalid
results or doesn't work at all.
Important: This defect has impact on basic functionality.
Useful: There is impact on the business, but only in a very
few cases.
Nice to have: The impact on the business is minor. Any user
interface defect not complicating the functionality often
gets this severity grade.

Hi to all..Now am working at one company as Software tester..I have selected for Accenture via one consultancy.. They have told that joining date will be on 19 th july..But now they are postponed joining date..whether i can trust that or not?Can u plz tell??plzz..whether i can put my paper to releive or not? CAn u telll?

0 Answers  

---

explan test metnodology/approch.... with example...

1 Answers  

---

Can you explain the concept of tailoring?

0 Answers  

---

When you will raise defect? before defect raising what you will do?

2 Answers   Cap Gemini,

---

wht is change management and configuration management?

2 Answers  

---

---

hi can anyone say how we can use test metrices in an applistion

1 Answers  

---

Tech round 1)joins 2)insert 3)delete 4)date 5)database architechture 6)bug life cycle 7)retesting 8)regression testing 9)somke and sanity testing Manager round 1)current organization details 2)explain current project 3)Basic unix comment 4)Test stragey

1 Answers   Thomson Reuters,

---

have u involved in reviws ? wt type reviews u done?

3 Answers   Accenture,

---

3) What is PDCA Cycle?

4 Answers   Mind Tree, Scope International,

---

1.For a single module how many builds are possible 2.what will be the max or min time to finish up an single module

0 Answers  

---

What is requirment phase testing?

1 Answers  

---

Suppose u got Change Request from client just before release, What is your approach and how do you convenience the client.

3 Answers   Cap Gemini,

---