Answer Posted / rahul

When ever the product company gathers some new information from the market place from some potential customers, they try to include it in their product and hence the requirement changes frequently.

In projects based applications, as one client only gives the requirements there are not many changes in requirements and hence testing also becomes less tedious than product testing.

In product based company, the tester will come out with creative idea about the products. He should think like a client/end user when changes were being made. products are basically should have less work and more out put to client.

Where as for applications , once it is done it will be implemented and maintenance work will be there once in a year as per the company policy

hello everybody, I have started learning testing tools and have familiarity with winrunner and general testing knowledge.Pl let me know what other stuff should i learn. I had 6 yrs of exp in GIS field and now i want to shift to testing tools. I left my job in 2001 now i want to enter into the market again. Could any of u help me how to approach the market. Any suggetions are very helpful to me. I am in US though. Thanks in advance

2043

---

What is 'fish pond analysis' with respect to software testing?

1057

---

Explain the term bug.

1255

---

What is recovery/error testing?

1117

---

What is your daily routine in your office?

2788

---

What is a test harness?

1196

---

how many types of automation frame works are there?

1204

---

In which phase should testing begin – requirements, planning, design, or coding?

1124

---

What is applications of FCOE?

2724

---

What is a 'walkthrough' in Software Testing?

1252

---

What is disaster recovery testing?

1074

---

What is parameter?

1101

---

What is qa engineer?

1073

---

wht is scope of ur project?

2149

---

Which activity in the fundamental test process includes evaluation of the testability of the requirements and system?

1293

---