What is the need of test planning?

To make proper plan of testing like schedule, resource identification, identifying staff, defining roles & responsibilities.

What can u do if the requirements are changed continuously?

- Work with the project's stakeholders early on to understand how requirements might change so that alternate test plans and strategies can be worked out in advance, if possible.
- It's helpful if the application's initial design allows for some adaptability so that later changes do not require redoing the application from scratch.
- If the code is well-commented and well-documented this makes changes easier for the developers.
- Use rapid prototyping whenever possible to help customers feel sure of their requirements and minimize changes.
- The project's initial schedule should allow for some extra time commensurate with the possibility of changes.
- Try to move new requirements to a 'Phase 2' version of an application, while using the original requirements for the 'Phase 1' version.
- Negotiate to allow only easily-implemented new requirements into the project, while moving more difficult new requirements into future versions of the application.
- Be sure that customers and management understand the scheduling impacts, inherent risks, and costs of significant requirements changes. Then let management or the customers (not the developers or testers) decide if the changes are warranted - after all, that's their job.

How do you scope, organize and execute a test project?

You used to organize and execute any work that was being assigned to you. Like
- I was keeping track of progress of each work item in an excel sheet.
- I reported weekly status reports to my lead explaining progresses made so far.
- When ever I felt that a particular work item was going to take more time than I expected, then I used to revise estimates and set new deadlines and inform the same to my lead.

How do you prioritize testing tasks within a project?

All the testing follows a Testing Process. Test Process is something which we have to execute in step by step. We cannot skip any of the process defined. Following is the Test Process which are in terms of their priority:
1- Preparation of Test Plan (Very important Step).
2- Preparation of Test Cases.
3- Execution of the Test Cases.
4- Defect report and tracking.
5- Test Report Summary.

What are the key challenges of testing?

1. Requirements are not freezed.
2. Application is not testable.
3. Ego problems.
4. Defect in defect tracking system
5. Miscommunication or no Communication
6. Bug in software development tools.
7. Time pressures

What is the difference between web testing and client server testing?

Desktop application runs on personal computers and work stations, so when you test the desktop application you are focusing on a specific environment. You will test complete application broadly in categories like GUI, functionality, Load, and backend i.e DB.

In client server application you have two different components to test. Application is loaded on server machine while the application exe on every client machine. You will test broadly in categories like, GUI on both sides, functionality, Load, client-server interaction, backend. This environment is mostly used in Intranet networks. You are aware of number of clients and servers and their locations in the test scenario.

Web application is a bit different and complex to test as tester don’t have that much control over the application. Application is loaded on the server whose location may or may not be known and no exe is installed on the client machine, you have to test it on different web browsers. Web applications are supposed to be tested on different browsers and OS platforms so broadly Web application is tested mainly for browser compatibility and operating system compatibility, error handling, static pages, backend testing and load testing.

In the web based testing, do you have test the back-end part?

Backend testing means mainly Database testing.
So you can say that we have not done any database testing, but in Harpo we used to change in the backend application and verify that in ORD (front end).
I think this will come under backend testing too.

When will be you start your testing?

We will prepare test cases as soon as we receive requirements.
We start test execution as soon a functional version of software is available.

What are the entry and exit criteria in the regression testing?

Entry Criteria of Regression Testing: When any change is made to the application.

Exit Criteria of Regression Testing: When all regression test cases executed and all defects are closed/verified.