Answer / bramhaji

compatability testing:
it is also known as portability
testing, during this test we will(test enggs) validates
that whether our application build is running on customer
expected platforms or not?
eg:operating sytems,compilers,browsers..etc
there are two types of compaltability problems we hav such
as forward compatability and backward compatability.

Configuration testing/hardware compatability:
during this test test enggs validates
whether the application build is suppporting different
technology hardware devices or not?
eg diff technologies of printers
" " " n/ws
" " popology n/ws.......etc

Answer / rohini

both are the concepts of non-functional testing
Compatibily is testing is done on platforms,"whether our
software is running on customer expected platforms or not"?
It is also called as portability testing.That means what
s/w we develop it should support all other operating
systems.

Configuration:Here we check whether pur s/w is supporting
all types of h/w devices.

Can anyone explein me the differences between Product Testing and Project Testing??????

7 Answers   FCG,

---

what is latentbug

5 Answers  

---

At what stage of the life cycle does testing begin?

6 Answers  

---

risk driven testing

1 Answers  

---

1. Test granularity refers to: a. Any way of determining the expected result for a test case. b. A quality improvement idea common in software development. c. The fineness or coarseness of a test’s focus. d. The impact of a bug on the system under

3 Answers  

---

4. A software error can be described as: a. A description of the relationship between two or more variables or set members in which the value of one does not influence the values of others. b. Any ill-advised, substandard, or temporary fix applied to an urgent problem in the (often misguided) belief that doing so will keep a project moving forward. c. The process in which developers determine the root cause of a bug and identify possible fixes. d. A mismatch between the program and its specification. 5. Select a reason that does not agree with the fact that complete testing is impossible: a. The domain of possible inputs is too large to test. b. Limited financial resources. c. There are too many possible paths through the program to test. d. The user interface issues (and thus the design issues) are too complex to completely test.

1 Answers  

---

anyone can tell me the example of high severioty and low priority ?

5 Answers   TCS,

---

What are the issues that u observed in the kick-off meeting?

7 Answers   Midas Technologies,

---

Explain Equavalence Partioning.With example?

3 Answers   CSC,

---

what are the testing appraoch that you have tested for Pencil

5 Answers   QA,

---

What steps are needed to develop and run software tests?

1 Answers   Crea,

---

what are the UAT bugs...why they come ??

2 Answers   Satyam,

---