Ans: Black box testing is a software testing method in which internal structure/design/implementation of item is being tested is not known to tester. This is mainly applicable to high level testing such as acceptance testing.
White box testing is a software testing method in which internal structure/design/implementation of item are been tested will be known to tester.

Ans: Automation testing is quite complex to test and existence of unrealistic expectations, poor testing practices and false sense of security, maintenance and other technical, organizational problems may occur. This testing can be successful when there are right people in the right environment.

What is extreme programming and what it got to do with testing?

Ans: Extreme programming is a software development approach for small projects on risk prone project with unstable requirements. Programmers are expected to write unit and functional testing code before the application is developed. Test control is under source control along the rest of code. Customers will be integral part of project team to develop and help scenarios for black box testing. The frequent re-scheduling, re-estimating and re prioritizing is expected in extreme programming.

How is testing effected by object oriented designs?

Ans: The well designed object oriented design can make it easier to trace the code to internal design to functional design to requirements. There will be slight effect on the black box testing because there is no requirement of understanding internal design of application.

How can World Wide Websites be tested?

Ans: Testing of websites takes long time because they are client/server based application with browser client and web server. While testing web applications firewalls, internet connections and applications that run in web application or pages will run on the server side. The expected load on the server, target audience, performance expected on client side, security and tracking of program should be kept in mind while testing the web applications.

How does client/server environment effect testing?

Ans: Client/server applications can be quite complex because of multiple dependency among the clients, hardware and servers. Thus testing can be extensive and when the time is limited it should be focused on system and integration testing. Additionally load or performance testing is used to determine the limitations and capabilities of client/server application.

Ans: It is required to work slowly over time to implement without stifling productivity. Then consensus should be used to reach the agreement on processes, adjust and experiment as an organization grows and matures.

What if the application has functionality that is not in requirements?

Ans: The functionality of the system has to be discussed among QA and development team in order to measure the impact on application with the indication of risk. If there is no enough time its then better to remove the function and declaration has to be done saying it has enhancement for future release.

What if project isn’t big enough to justify enough testing?

Ans: Impact of project errors is to be considered not the size of project. However if extensive testing is not justified than risk analysis is again needed to be considered.

What can be done if requirements are changing continuously?

Ans: If requirements are continuously changing than testing should be done prioritizing the features. It should be ensured that common flows are all tested as much as possible.