Here are some Software Testers Interview Questions

1What is the role of QA in development project?
Deploy and enforce standards Continually improve standards, QA process based on previous experiences, Promote effective means for reporting and communication.
2What is verification?
A: Verification ensures the product is designed to deliver all functionality to the customer; it typically involves reviews and
meetings to evaluate documents, plans, code, requirements and specifications; this can be done with checklists, issues lists, and
walkthroughs and inspection meetings.
3What is validation?
A: Validation ensures that functionality, as defined in requirements, is the intended behavior of the product; validation typically involves actual testing and takes place after verifications are completed.

What is quality?
A: Quality software is software that is reasonably bug-free, delivered on time and within budget, meets requirements and expectations and is maintainable
What is good code?
A: A good code is code that works, is free of bugs and is readable and maintainable.
What is good design?
A: Design could mean to many things, but often refers to functional design or internal design. Good functional design is indicated by software functionality can be traced back to customer and end-user requirements. Good internal design is indicated by software code whose overall structure is clear, understandable, easily modifiable and maintainable; is robust with sufficient error handling and status logging capability; and works correctly when implemented.
What is software life cycle?
A: Software life cycle begins when a software product is first conceived and ends when it is no longer in use. It includes phases
like initial concept, requirements analysis, functional design, internal design, documentation planning, test planning, coding,
document preparation, integration, testing, maintenance, updates, re- testing and phase-out.
What is the role of documentation in QA?
A: Documentation plays a critical role in QA. QA practices should be documented, so that they are repeatable. Specifications, designs, business rules, inspection reports, configurations, code changes, test plans, test cases, bug reports, user manuals should all be documented. Ideally, there should be a system for easily finding and obtaining of
documents and determining what document will have a particular piece of information. Use documentation change anagement, if possible.


Continue Reading On
https://sharptester.com/2017/10/20/software-testers-interview1/