WDV 331 Dreamweaver Applications. Testing your site Dreamweaver CS6 Chapter 16. Site Launch Checklist. Don’t wait until you finish your site before you develop a thorough strategy for regular testing .
PowerPoint Slideshow about ' WDV 331 Dreamweaver Applications' - jocelyn-cleveland
An Image/Link below is provided (as is) to download presentation
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Live view doesn’t necessarily show you how your page will look in other popular browsers, like Internet Explorer, Firefox, or Opera.
Use Dreamweaver’s Preview command (File → Preview in Browser) to test your pages in every browser you can get your hands on.
Thorough evaluation, however, you should preview your pages using every combination of browser and operating system you think your site’s visitors may use. At the very least, try to test your pages using Internet Explorer 7, 8, and 9 on Windows; Chrome on Window PCs and Macs; Firefox on Windows and Macs; and Safari on the Mac.
According to the Market Share website ( http:// bit.ly/ q7UEdA ), Internet Explorer 8 for Windows is still the most popular web browser, followed by Internet Explorer 9, Chrome, and Firefox. Including all versions, Internet Explorer claims over 53 percent of the worldwide market for browsers (as of January 2012).
HTML and CSS errors can easily slip into your code if you edit your files with a text editor or work on pages someone else created. These errors, called validation errors, are often the source of cross-browser display problems, messed-up layouts, and incorrect formatting.
CS6 use the industry-standard W3C validator. The W3C, or World Wide Web Consortium, develops most of the technologies web designers rely on, like HTML and CSS, and they’ve always provided a very good validator. The validator resides online, but Dreamweaver CS6 makes the testing process simple by incorporating it File → Validate → Validate Current Document (W3C).
Dreamweaver’s Check Links Sitewide command scans an entire site’s worth of files, and reports all the links and paths that don’t lead to a file. (It’s one of Dreamweaver’s site management features, meaning that you have to set up a local site before you can use this command.
Dreamweaver checks only links and paths within the local site folder; it doesn’t check links that lead to other people’s sites
If your local site contains a lot of pages, you can exclude files from the Check Links Sitewide operation using the Cloaking feature described on Cloaking Files . Makes the link-checking operation go faster.
It’s always the little things. When you build a website, small errors inevitably creep into your pages. While not necessarily life-threatening, forgetting to title a page or add an Alt property to an image does diminish the quality and professionalism of a site. Use Dreamweaver’s site-reporting feature to quickly identify these problems
Dreamweaver adds the correct tags in the correct order. But there are exceptions to every rule. In the process of formatting text, deleting elements, and — in general — building a web page, it’s quite possible to end up with less-than-optimal HTML. While Dreamweaver usually catches potentially sloppy code, you may nonetheless run across instances of empty tags, redundant tags, and nested tags in your Dreamweaver pages.
It’s best to first use the Site Reports feature (see Site Reporting ) to identify problem pages.
Open a web page you want to clean up.
Choose Commands → Clean Up HTML (or Clean Up XHTML).