“I bought this guide a few days ago to prepare for my interview with Oracle. Many of the questions they asked me were from this guide. I found this book absolutely great!”
whether is taking right input and giving right output, whether all the output conditions expected are meet, which really can crash the system, checking the boundary conditions which really annoy the user, hanging etc. which can cause loss of data, like memory corruption, memory leaks etc
the above answers are not correct… if you are a tester, ask the developer or the manager for more time or simply automize a part of testing so that multiple parts of the system can be tested in parallel. The product should and cannot be shipped without complete testing.
The goal of any project is to test the entire code base, but in reality that doesn’t always happen. In many cases a ’ship date’ is dictated and changing it, to allow more testing, is not in a company’s best interests.
The quality of a product is a factor similar to features and resources required.
Testing for most products should be prioritized the same way features are. Automate as much as possible and ensure that the most important features are tested.
the requirements of a system do not dictate tests. the system is always VALIDATED against the requirements…as for the tests, they can be activites performed throughout the SDLC that will aide the testing process….such as unit testing, integrations testing, system testing, acceptance testing, installation testing and finally maintainance !! (all in order)
I will ask the interviewer for the definition of “remove” first. If ( the answer is dig a hole, let water bubble up) { I would say I “remove” a state lack of water supply. } else if ( the answer is give it up or give it away to other countries ) { I would say it’s some state with the biggest area of desert. And I would definitely trade sth. back from whom want it } else // default, { I will keep it for possible future usage }
I would first ask if I have to give up one of the states. If so I would give up West Virginia since it is not and economic epicenter and the face the US would maintain boarders around the state thus leaving us with positive control if needed.
South Carolina cause the legal age of consentual sex is 14 and the driving age is 15. And the STD rate is number 1 in the country while the SAT score average is #50 in the US. No one with any worth whatsoever lives there.
Since this is supposed to be a question to test someone’s analytical skills, I would say that I would analysis states cost to federal government programs against income/tax contributions and the state with the largest draw and least contribution would be removed.
I would not remove any of them, (provided the definition of state is the USA’s states). Could you imagine the gerrymandering after something like that? Besides - each state has something special it brings to it’s star on the flag. That is what makes the USA so remarkable.
You can always remove the DEAD States. If there are 50 states (FORMAL LANGUAUES / Theory of Computation), any dead state is truely useless, as it leads you no-where. So delete the DEAD State
there are two possible solutions….one is to remove a border between two states (perhaps the border between North and South Dakota), thus making the two states now one, therefore giving you 49 states, or; giving Maine to Canada as it is not as important militarily or economically as the only other two possibilities, Hawaii and Alaska.
In order to get the product in time, remove in this order:
1. unused state in real world ordered by the probability of being reached by customers
2. remove the states which can be handled by workarounds
3….
benefist:
1. everibody is happy with a solid product
2. it can make money
3. it does not spend money on support
4. it can make money on custom servicces
5. if still desired, it will apear in future releases
You want to see if removing a state causes any “bad” stuff to happen.
So for instance, if remove means killing people off then you want to remove a state with the lowest population count.
If people are not killed but are just evacuated then you want to remove the state with the least natural resources or income (So Alaska/Hawaii are not on the list).
If it is to merely move it off to another country like Canada, then again look to see if the states on the border with least income to the country can be let off.
If it is just for fun - I’d go with the one that gave birth to terrible presidents but presumably they have resources which funded their climb to power!
The answer should be dependent on the definition of states. Does it relate to the state of being/existence/result of a computation/geopolitical entity?
First clarify “states” and “remove” and whether this choice is 0, 1, 2, etc. state removal. Next try to access the full potential negative consequences (N) of removal over some period of time (of interest). We need some objective function, N. If forced, then minimize N over removal. If combining two states is an option, then find two for which this combining causes minimal N and compare to absolute removal. If “states” refers to US states, then follow legal code; the workplace is no place for political bias (unless you work for Fox News;), which may be the objective of this question. If legal code does not exist, then take a vote. Pick the one(s) with the least % objections (or most favored); some may even want to leave.
First make sure that the law allows it. Zero in on the state whose revenue contribution is lesser than the amount spent on maintaining it. Then ask the natives of that state if they’re happy with the removal of that state from US. Pass the bill only if majority(actually more than 2/3) of the people agree to it.
If the question merely asks for reduction in the number of states by 1, merge those 2 adjacent states which minimizes maintenance overhead.
prioritize what you want to test, in the order,
whether is taking right input and giving right output,
whether all the output conditions expected are meet,
which really can crash the system, checking the boundary conditions
which really annoy the user, hanging etc.
which can cause loss of data, like memory corruption, memory leaks etc
Use the requirements to dictate your tests. If your product satify the requirments, then you can ship it.
That’s how they do it a MS.
the above answers are not correct…
if you are a tester, ask the developer or the manager for more time or simply automize a part of testing so that multiple parts of the system can be tested in parallel. The product should and cannot be shipped without complete testing.
The goal of any project is to test the entire code base, but in reality that doesn’t always happen. In many cases a ’ship date’ is dictated and changing it, to allow more testing, is not in a company’s best interests.
The quality of a product is a factor similar to features and resources required.
Testing for most products should be prioritized the same way features are. Automate as much as possible and ensure that the most important features are tested.
the requirements of a system do not dictate tests. the system is always VALIDATED against the requirements…as for the tests, they can be activites performed throughout the SDLC that will aide the testing process….such as unit testing, integrations testing, system testing, acceptance testing, installation testing and finally maintainance !! (all in order)
Obviously, Alaska and Hawaii since they’re not directly connected to the main portion of the US.
Plus, since Alaska is up north, let Canada keep it.
PS. I AM CANADIAN
Florida.
See: Bush.
O.K., so I could. Who says I would?
What does “remove” mean? Would it kill the inhabitants (or would they flee first)? Would it leave a hole?
I will ask the interviewer for the definition of “remove” first.
If ( the answer is dig a hole, let water bubble up)
{
I would say I “remove” a state lack of water supply.
}
else if ( the answer is give it up or give it away to other countries )
{
I would say it’s some state with the biggest area of desert. And I would definitely trade sth. back from whom want it
} else // default,
{
I will keep it for possible future usage
}
hawaii - because it’s the only state that can be removed without affecting any surrounding land.
California
PS: why the hell everythings going up here..
New Jersey.
I had to live there for two years.
Believe me, we could do without it.
<Just kidding of course>
I would first ask if I have to give up one of the states. If so I would give up West Virginia since it is not and economic epicenter and the face the US would maintain boarders around the state thus leaving us with positive control if needed.
South Carolina cause the legal age of consentual sex is 14 and the driving age is 15. And the STD rate is number 1 in the country while the SAT score average is #50 in the US. No one with any worth whatsoever lives there.
There are actually an infinite number of states, I’d remove all pertaining to boredom (Chineses curse, may you live in interesting times).
US, all of them. Why? ’cause there is no need in US at all.
Since this is supposed to be a question to test someone’s analytical skills, I would say that I would analysis states cost to federal government programs against income/tax contributions and the state with the largest draw and least contribution would be removed.
Jeesh speaks like a true American
I would not remove any of them, (provided the definition of state is the USA’s states). Could you imagine the gerrymandering after something like that? Besides - each state has something special it brings to it’s star on the flag. That is what makes the USA so remarkable.
Texas, because — well isn’t it obvious?
This is a really, really stupid question that has nothing to do with software development.
You can always remove the DEAD States. If there are 50 states (FORMAL LANGUAUES / Theory of Computation), any dead state is truely useless, as it leads you no-where. So delete the DEAD State
there are two possible solutions….one is to remove a border between two states (perhaps the border between North and South Dakota), thus making the two states now one, therefore giving you 49 states, or; giving Maine to Canada as it is not as important militarily or economically as the only other two possibilities, Hawaii and Alaska.
In order to get the product in time, remove in this order:
1. unused state in real world ordered by the probability of being reached by customers
2. remove the states which can be handled by workarounds
3….
benefist:
1. everibody is happy with a solid product
2. it can make money
3. it does not spend money on support
4. it can make money on custom servicces
5. if still desired, it will apear in future releases
Combine two states into one. Not frorm US so dont know combining which two works out best.
Its not stupid question. If some of your modules cannot be shipped on release date, which one will you remove Sir? Thats the intent.
You want to see if removing a state causes any “bad” stuff to happen.
So for instance, if remove means killing people off then you want to remove a state with the lowest population count.
If people are not killed but are just evacuated then you want to remove the state with the least natural resources or income (So Alaska/Hawaii are not on the list).
If it is to merely move it off to another country like Canada, then again look to see if the states on the border with least income to the country can be let off.
If it is just for fun - I’d go with the one that gave birth to terrible presidents but presumably they have resources which funded their climb to power!
I’d get rid of Alaska, simply to end the arguments over what “continental US” means.
California - since Google is based there!!
Just kidding, of course !!!
The answer should be dependent on the definition of states. Does it relate to the state of being/existence/result of a computation/geopolitical entity?
The answer is different for the different cases.
This is a misleading question.
First off, we were told that we could get rid of any state.
However, nothing in the question said that we must. In effect, we have 51 options.
Given the opportunity to remove any state, without the expressed necessity to do so, I wouldn’t remove any.
First clarify “states” and “remove” and whether this choice is 0, 1, 2, etc. state removal. Next try to access the full potential negative consequences (N) of removal over some period of time (of interest). We need some objective function, N. If forced, then minimize N over removal. If combining two states is an option, then find two for which this combining causes minimal N and compare to absolute removal. If “states” refers to US states, then follow legal code; the workplace is no place for political bias (unless you work for Fox News;), which may be the objective of this question. If legal code does not exist, then take a vote. Pick the one(s) with the least % objections (or most favored); some may even want to leave.
All the 50 states where the degree of philanthropy/ humanity or altruism is least…
5 or 0
First make sure that the law allows it. Zero in on the state whose revenue contribution is lesser than the amount spent on maintaining it. Then ask the natives of that state if they’re happy with the removal of that state from US. Pass the bill only if majority(actually more than 2/3) of the people agree to it.
If the question merely asks for reduction in the number of states by 1, merge those 2 adjacent states which minimizes maintenance overhead.
Regards,
J1g54w ( feedback: spamcollectiontool@gmail.com )
Leave an Answer/Comment