Introduction of Dynamic Pages

Dynamic Pages are typically written in various scripting languages or technologies such as ASP, PHP, Perl or JSP.

Advantages

• Offers highly personalized and customized visitor options.
• Database access improves the personalized experience (as opposed to using just client side
cookies)
• Scripts can read in data sources and display it differently depending on how it is run.
• Can create the illusion of being updated regularly using time and date sensitive routines (or
even randomisers) to display pre-written text.

Disadvantages

• Personalized pages are not very cache friendly.
• Requires a basic minimum knowledge of the language being used.
• Scripts need more consideration when uploading and installing, particularly to Unix-related
servers.

What is CSS Stands For?

CSS stands for Cascading Style Sheets,Styles define how to display HTML elements,Styles are normally stored in Style Sheets ,Styles were added to HTML 4.0 to solve a problem,External Style Sheets can save you a lot of work,External Style Sheets are stored in CSS files,Multiple style definitions will cascade into one

Web Testing Interview Questions?

1. Describe some of the possible web page futures.

2. Question: What are possible configurations that could affect the testing strategy of any web
site?
Answer: Hardware platform (PC, Mac), Browser software and version, Browser Plug-Ins, Browser settings options, Video resolution and Color Depth, text size,

3. What is website usability testing.
Ans:- Usability testing is a technique used to evaluate a product by testing it on users…Testing to check “User Friendliness”

4. Why spell checker is not enough during testing spelling on web page?
Ans:- Because there are Pictures/Logos/Photos that may contain wrong spellings and the spell checker is not able to identify those errors.

5. Question: Name a few website mistakes that could cause configuration and compatibility bugs.
Answer: Non standard colors, frames, tables etc.

6. Question: What the latest web technologies do you know?
Answer: RSS,

7.Question: Name some Alternative Browsers.
Answer: Opera, Mozilla

8. Describe some Caching Issues.
:-Cache is
A) HTML meta tags to prevent page caching. Every single possible combination and none work.
B) PHP Headers to prevent page caching. Every single possible combination and none work.
C)Proxy server caching issues.
NOTE:-So its slow down the overall Performance of the system. So we used to clean up the old cache time by time.

9. What HTML standard do you know?
10.What web specific types of testing do you
know?

11.What is static and what is dynamic web page?
12.Question: Can the Netscape scripting host without plug-ins run Microsofts JScript on the
client side?
Answer: No

13. Question: What is Glyphs?
Answer: Glyph is the picture of the character.

14.What techniques will cause double-byte problems to show up?
Ans:- ColdFusion MX is not compatible for unixs(Solaris).

15. What is Alt Key Input?
16. How will you decide when and what to test during performance testing?
17. Question: What types of web testing security problems do you know?
Answer:(Denial of Service (DoS) attack, buffer overflow)

18. Question: What types HTTP Response Codes do you know?
Answer: ( 2xx – success, 3xx – Redirection, 4xx – Client Error, 5xx – Server Error)

19. What errors can occur when the page loads?
20. What are the metrics what can be used during performance
testing?
21. What HTML file extension can be used?

22. What are the differences between testing WEB application and testing client-sever
application?
23. Write test cases for Search Engine?
24. Difference between HTTP and HTTPS? Explain how the data is secured in
HTTPS?
25. What does DNS contains?
26. What is the difference between authentication and authorization?
27. What type of security testing you performed?
28. Difference between GUI and Usability Testing

Testing Under Time Pressure

Here are some points to be considered when you are in such a situation:
1) Find out Important functionality is your project?
2) Find out High-risk module of the project?
3) Which functionality is most visible to the user?
4) Which functionality has the largest safety impact?
5) Which functionality has the largest financial impact on users?
6) Which aspects of the application are most important to the customer?
7) Which parts of the code are most complex, and thus most subject to errors?
Which parts of the application were developed in rush or panic mode?
9) What do the developers think are the highest-risk aspects of the application?
10) What kinds of problems would cause the worst publicity?
11) What kinds of problems would cause the most customer service complaints?
12) What kinds of tests could easily cover multiple functionalities?
Considering these points you can greatly reduce the risk of project releasing under less time constraint.

Why We Need Testers?

There are number of reasons for which we need dedicated testers and not developers:

1. The perception between a developer and a tester is different. Tester has an attitude to break and will cover both positive flows and negative flows.

2. Tester not only have a very good understanding of various flows and modules in an application, he also applies his skill and expertise to find bugs.

3. A tester not only concentrates on functionality but also on other issues like usability, GUI, Database

We always need a Separate Testing team to Ensure the Quality of the Product. Reason Being:

A Developer will never tend to find a Bug in his code, where as Tester’s main motive is to find as many bug as possible.
A developer can overlook minor issues where as a Tester will not overlook even the minor things, ensuring that cutomer is fully satisfied.

1.we need testers because developers are not good testers.
2.Misunderstanding will not be detected ,because the checker will assume that what the other individual heard from him was incorrect.
3.Improper use of the development process may not be detected because the individual may not understand the process.
4.The individual may be blinded into accepting erroneous system specifications and coding because he falls into the same trap during testing that led to the introduction of the defect in the first place.
5. Information services people are optimistic in their ability to do defect free work and thus sometimes underestimate the need for extensive ttesting.
6.Without formal division between development and test, an individual may be tempted to improve the system structure and documentation, rather than allocate that time and effort to the test.