Answer / priya

Unit Testing is a testing done to check if the new code is working properly before delivering the build to testing team

Integrating testing is testing done when we move from one screen to an other screen or when two integrated modules are tested.
Acceptance testing is done when the product is delivered to the customer for him to accept.

Static checking is primarily the syntax checking or a manual review of the code.

smoke testing is tsting the most important functionality without going much deep into it when there's a new application delivered to testing team.

system testing is testing done on a completely integrated system to know it's compliance with the requirement.

Load testing is done to know if the application can work normally under the defined number of user and if the response is alright even under that load


soak testing is a testing done to see how long the system can with stand with the no of users for a particular duration of time.

scalability testing is done to know how many extra users can use the application beyond the load specified.

sanity testing is done after a new build to know if the important features are working propely .

Ramp testing increases the no of user in a particular timeframe to know tha max no of user that it can accomadate before throwing error messages.

monkey testing is something thatu do to test without following any document and some random unusal testing

gray box testing is the combination of unit testing and balck box testing

functional testing is a testing done on function by giving some input and expecting some output

glass box testing is a structural testing where the test is derived by directly seeing the code.

dynamic testing is nothing but the black box testing itself.like testing a functionality by giving input and expect a output ..

compatability testing is done on differnt browsers to see if the response is same or if doesn't load properly.

concurrency testing is done to see if two users use the application parallely how tha application responds and how the data is handled.

component testing is same as unit testing except for stubs and stimulators removed.

adhoc testing is a negative tsting, testing done with an unwexpected situation or that 's not there in the requirement documents

agile testing -testing usiong the agile model.

How you will write test cases on DROP DOWN list BOX on GUI

5 Answers   eMids, Valtech,

---

Why is it that the boundary value analysis provides good test cases?

0 Answers  

---

IF A > B THEN C = A – B ELSE C = A + B ENDIF Read D IF C = D Then Print "Error" ENDIF A. 1 test for statement coverage, 3 for branch coverage B. 2 tests for statement coverage, 2 for branch coverage C. 2 tests for statement coverage. 3 for branch coverage D. 3 tests for statement coverage, 3 for branch coverage E. 3 tests for statement coverage, 2 for branch coverage

1 Answers   ISTQB,

---

Using the same code example as question 17,how many tests are required to achieve 100% branch/decision coverage? A. 1 B. 2 C. 3 D. 4

1 Answers   ISTQB,

---

what are the test case scenario for epos/pos testing,and how to initiate the process

0 Answers  

---

Requirement from Market “Alice is talking to Bob. Bob thinks that Alice should talk to Chris for more information. Currently, Bob will pass on the directory number of Chris to Alice; Alice/Bob will disconnect the call and then Alice will initiate a new call to Chris. What we need need, Bob should be able to transfer the call to Chris, without Alice making another call.” Implementation done by Unified CM Development Team When a basic call is connected, a new softkey “Transfer” will be displayed on the IP Phone. User (say, Bob) can press that and dial a target (say, Chris). Bob has two options (1) wait for Chris to answer and then tell Chris about call from Alice and then press “transfer” again to complete transfer (2) press “Transfer” immediately; when Chris answers he will be connected to Alice Please come up with test cases thinking from a user perspective, let’s say from a Bank (there could be users such as receptionists, accountants, managers etc.) – in what all scenarios transfer can happen, any negative scenarios (cases where we don’t get a positive response always). If you think you need an enhancement to the feature, please go ahead and suggest that as well.

0 Answers  

---

Credit card field contains four text boxes. We can validate each textbox separately with conditions but how can we write integrated testcase for all the four?

1 Answers  

---

Write test cases to test a browser app

0 Answers  

---

Explain the state testing?

0 Answers  

---

explain with examples- transaction testing, syntax testing, domain testing, logic testing, and state testing.

1 Answers  

---

How to write test cases for lift?

0 Answers  

---

What is port testing ?

1 Answers  

---