- How do you analyze your test results? what metrics do you try to provide?
How do you view test results?
Test log is created for analyzing the test results.This is a chronological record of the Test executions and events that happened during testing. It includes the following sections:
Description: What’s being tested, including Version ID, where testing is being done, what hardware and all other configuration information.
Activity and Event Entries: What happened including Execution Description: The procedure used.
Procedure Result: What happened. What did you see and where did you store the output?
Environment Information: Any changes (hardware substitution) made specifically for this test.
Unexpected Events: What happened before and after problem/bug occurred.
Incident/Bug Report Identifiers: Problem Report number
- If you come onboard, give me a general idea of what your first overall tasks will be as far as as starting a quality effort?
Try to learn about the application, Environment and Prototypes to have the better understanding of application and existing testing efforts
- How do you differentiate the roles of Quality Assurance Manager and Project Manager?
Quality assurance manager responsibilites includes seting up the standards, the methodology and the strategies for testing the application and providing guidelines to the QA team. Project Manager is reponsible to testing and development activities.
- What do you like about QA?
QA is the field where in one will be working to multiple environments and can learn more.
- Who in the company is responsible for Quality?
Both development and quality assurance departments are responsible for the final product quality.
- Should we test every possible combination/scenario for a program?
Ideally, yes we should test every possible scenario, but this may not always be possible. It depends on many factors viz., deadlines, budget, complexity of software and so on. In such cases, we have to prioritize and thoroughly test the critical areas of the application.
- What is client-server architecture?
Client-server architecture, a client is defined as a requester of services and a server is defined as the provider of services. Communication takes place in the form a request message from the client to the server asking for some work to be done. Then the server does the work and sends back the reply.
- How Intranet is different from client-server?
Internet applications are essentially client/server applications – with web servers and ‘browser’
- What is three-tier and multi-tier architecture?
A design which separate (1) client, (2) application, and (3) data each into their own separate areas which allows for more scalable, robust solutions
A three-tier system is one that has presentation components, business logic and data access physically running on different platforms. Web applications are perfect for three-tier architecture, as the presentation layer is necessarily separate, and the business and data components can be divided up much like a client-server application