31. If automating - what is your process for determining what to automate and in what order?
Which test case to automate: 1: test cases that need to run for every built.(also called sanity testing) 2: test that uses multiple set of data values for same action(called data driven testing). 3: identical test that need to be executed 4.mission critical pages that won’t change in short term.
32. Tell me about the best bug you ever found.
We do manual testing on printers/MFP's. The best bug i was found in the pre-gold release of product, i.e printer is not printing due to improper build
33. What made you pick testing over another career?
I am very proud be as a tester because a tester needs to know each and every activities in the SDLC, and his role in more important/ responsible when the quality aspects are concerned. If a developer makes a mistake that can be resolved by a tester but if tester makes mistake and if the customer find a bug then it will cost high.
34. When should testing start in a project? Why?
Functionality of the product depends on coding & coding is done according to the requirements. if the requirements aren’t clear, the resultant product is not a quality product. Hence testing starts right from the requirements. once the requirements are done feasibility study is done on design functional specifications
35. How do you go about testing a web application?
It’s clear that for testing any application, one should be clear about the requirements and specification documents. For testing Web application, the tester should know, what the web application deals with.
36. Would you like to work in a team or alone, why?
TEAM: Together Everyone Achieves More. The software testing is teams work with more focus on testing individual modules/functionality, which are related to the functionality of everyone in the team. I would like to work in a Team as well as individually
37. Give me 5 strong & weak points of yours
willing to work in a team and as an individual whenever needed. Strong communication skills, Strong desire for quality, able to communicate with both technical and non-technical people. Always ready to learn new skills.
38. When should testing be stopped?
When the test manager is confident that the application will perform as expected in the production environment. This confidence is derived by analysis conducted on: a) Deadlines (release deadlines, testing deadlines, etc.) are met b) Test exit criteria are met 3. Functionality is tested 4.Test budget is depleted
39. What sort of things would you put down in a bug report?
Usually bug report contains. * path ( module / link) * bug severity * posted by * assigned to * status * resolution * screen shots for reference
40. Who in the company is responsible for Quality?
I feel that Quality is every individual's responsibility wherein he/she contributes towards it in their own way. In real time clients should define Quality.
41. Who defines quality?
To measure the Quality several are there. some of them are 1. correctness 2. reliability 3.maintainability 4. portability 5.interoperability
42. What is an equivalence class?
If a set of object can be linked by a relationship that is symmetric, reflexive and transitive then we can say there is equivalence class. Using this concept Equivalence Partitioning method of Black Box Testing divides the input domain of a program into classed of data from where test case can be derived. Ideally each testcase can uncover class of errors that might otherwise require many testcase t5o be executed before general error is occurred.
43. Is a "A fast database retrieval rate" a testable requirement?
No. But this can be a testable if the requirement is clear and specifies the acceptable range of retrieval rate i.e. less than 1 second etc.
44. Should we test every possible combination/scenario for a program?
Use boundary value analysis technique and equivalence class. Using that we can reduce the no of possible combination
It depends on the project, which we are working. If the project is customizable and used by several clients after small changes to the product.
No comments:
Post a Comment