Interview Question
Team: QA
Country: United States
is a comprehensive book on getting a job at a top tech company, while focuses on dev interviews and does this for PMs.
CareerCup's interview videos give you a real-life look at technical interviews. In these unscripted videos, watch how other candidates handle tough questions and how the interviewer thinks about their performance.
Most engineers make critical mistakes on their resumes -- we can fix your resume with our custom resume review service. And, we use fellow engineers as our resume reviewers, so you can be sure that we "get" what you're saying.
Our Mock Interviews will be conducted "in character" just like a real interview, and can focus on whatever topics you want. All our interviewers have worked for Microsoft, Google or Amazon, you know you'll get a true-to-life experience.
This is very generic question.
- Victor April 08, 2012Some thoughts on API testing/validation - note that the list is not extensive...but in my opinion, these are few points to consider:
1. Return value validation - this the is validation done on the expected return values for a given set of input.
2. Input validation - given a set of input, what is the expected behavior of the function. This includes, possible return values, effect on the environment, outputs, etc.
3. Logging validation - this is important aspect we sometime ignore. Given failures, how it is useful in debugging the issue upfront rather than stepping into the function.
4. Stability of the API - possibly when called frequently.
5. Memory leaks
6. Semantics - this is sometimes important from what is the intent and the function signature
7. Overflow and underflow conditions
8. Boundary values validation
9. Equipartition of the set of inputs.