Answer / inder

TC1: Does the calculator turn on when teh on button is pressed
TC2: Does itdisplay the number on teh screen that was pressed
TC3: If we enter 2 and then the plus symbol "+" and then
enter2 again,then does it display the answer "4" or not.
TC4: Same way for all the buttons like *,/,-,%, square roots
and all
TC5: When we press the clear button then is the screen
display reduced to "0" or not

Answer / nona

in addition to the above,

1- what is the calc output incase of dividing by zero
2- what is the calc output incase of sqrt a negative number
3- Number.Oper.oper.numer= << for example 1+-3= << it
should take the last operator
2- test the back space.. should delete last digit but
incase of (.) it should be deleted with the number to the
left and input 0 (^_^) for example: (2.1) --> backspace
gives (2.) then backspace again .. it should give 0 NOT 2

Answer / nagk24

Functional:-
1)verify the turn on
2)verify the display
3)verify the all buttons working or not
4)perform operations like +,-,*,/ etc
5)verify the outputs and compare to the expected results

Non-functional:-
1)verify the weight
2)verify it is easy to hold
3)verify visibility of screen
4)verify buttons are comfortable

Answer / shyam

1)to verify the all the buttons
2)to verify the timer is working or not
3)to verify the(+,/,*,-) operations./
4)to verify the edit option
5)when we enter some values in caluculator , whether it is possible to delete the last digit or not
6)combination of arithamatic operations working or not
7)to veriy the data is visible or not
8)to verify the operation like(when i enter (0-55) the answer should be -55)displayed.
9)to verify the power on/off
10) when we use divide operation the example (like 33/6 then the answer should display quotient not a remainder)
11)to verify the max and minimum values.
12)when we enter float values like (1.5, it should be display float value only not a round value =2)
13)verify the batteries
14)to verify the reusable or not
15)to verify the performance
16)to verify the storage values
17)to verify the recovery values(when caluculator get crashed it will be recovery or not)
18)to verify the comfortability
19)when we enter 2 values without using eual(=) operator ,it should be display last value
20)when we press two buttons at a time we verify the caluculator is understandble or not..

Answer / ehsan

Hi, I have got following requirement for interview question, so how should i write test cases for them?
- user should be able to enter at least 10 character using mouse.
- user should be able to enter at least 10 character using keyboard.
- user should be able to enter at least 10 character using number block.
- user expects, that calculator display corresponding title
- user expects using arabic number for calculation
- user must be able to do calculation in rational space
- user should be able to do addition of 2 digits and see the correct result by Enter or mouse over
- user should be able to do multiplication of 2 digits and see the correct result by Enter or mouse over
- user should be able to delete last input using CE
- user should be able to delete all input using C and go back to exit state
- user should be able to save a number using M+ and recall it later
- saved digits should be displayed using MR
- user should be able to add a digit to already saved digit using M+
- user should be able to subtract a digit from already saved digit using M-
- user should be able to clear memory using MC


does anybody have idea?

Answer / madhulika.

BASIC FLOW:
1. Verify user is able to open calculator.
2. Verify basic operations are working (+,-,*,/).
3. Verify numbers are working.
4. Verify close button works.
5. Verify max/min works.
ALTERNATE FLOW:
1. Verify memory add delete works.
2. Verify other operation like %, sqr, backspace, copy, correction works.
3. Verify if help works.
4. Verify Edit works.
5. Verify if all options in View works.
EXCEPTIONAL FLOW:
1. Verify if providing invalid value like divide by 0 displays appropriate error.
2. Verify sqrt of negative number.
3. Verify max/min number which can be entered in calculator, and if it is per SRS.
--------------------------------------------
The similar flows for online calculator except that user will have to provide the link to open a calculator.
Exceptional case would include to verify the error displayed when the link is down.

Answer / suresh

1.verify the basic test cases on calc like to check display,on/off buttons,operating buttons like +/*-,numbers from 0-9,advance functions like trigonometry functions,storage key button etc.

2.validating the functionality like BODMAS and advance keys related actions,trigonometry functionality.

3.verifying the performance like speed of the calculation,wait of the calculator,battery range /works fine with solar,display narration ,on/off button speed of action.

Answer / vamshi kumar

1)to verify the buttons is working or not

2)to verify that whenevr doing the operations the battery is(avaliable) there or not

3)to verify the battery is working or not

4)to verify the user reqirements like digits(0-9) and operations(+,/,*,-,=) is avaliable or notin the calaculator

5)to verify the display is visible and clear or not

6)to verify the bolts is fixed or not

7)to verify that if it is droped several height it should be strong or not

8) to verify the buttons is smooth or not

9)to verify the flexible to hold or not

10)to veirfy the calucalator is working with battery or solar

11)to verify the operation is doing correct or not (like if we perform addition the value is enterd 2 time's the result is

4 or not

Hi friends, Im an MBA Finance, 2 yrs of exp workng in Investment com, + around 2 yrs of exp in Manual testing in Finane domain. Im looking for manual testing jobs but not getting any calls, Im worried is manual tesing in finance domain do have any good scopes in future or not. Plz provide me ur valuable suggestion,so tht I can best decision to retain in this platform(manual testing). or not

0 Answers  

I m writting the test cases in Excel sheet. After wrting test cases for version 2.0.0 If there is new feature added in build 2.0.1, I will write test cases for newly added feature. Then 3.0 version release for testing with new feature. I will write test cases for newly added feature 3.0 But if in between 2.0.2 build release for testing with same feature of 3.0.Then should I have to write test cases for same feature again? If not --> when 2.0.2build again release for testing after 2months then How should I came to know that I have to run these test cases on 2.0.2build?

2 Answers  

how do u find out memory leaks in any application..?

2 Answers  

tell me the V-model advantages & disadvantages

4 Answers   QA,

In an ATM machine , after entering pin -> not able to withdraw money. What are all the possible reasons. Debug

2 Answers   Amazon,

which situation will decide the approach (topdown/bottom up) to choose from?

2 Answers  

What all document are required to testing?

7 Answers   NIIT,

how to write a testcase for coke vewnding machine

1 Answers  

what is the quality?

8 Answers   AppLabs,

While executing test cases, you got a test case as failed and it has a high severity(Show stopper). What is the next step? How you will execute the remaining test cases ?

3 Answers  

what is suspension criteria in your test paln and explain one suspension criteria in your test paln,... pls give one real time example

3 Answers   Satyam,

Explain your web application archtechture?

1 Answers   Verizon,