Web Presentation Guide 5.1
Test User Environment
Action
Test a Web site prior to publication to ensure that it works properly, does what it is intended to do, and does not compromise hardware and data.
Why
Mistakes, oversight, and configuration problems can erode user confidence in site content, misconstrue perception of the agency, and compromise agency servers and data. Conform to consistency, functionality, usability, compatibility, and security best practices across the agency. Use multiple environments as a last means of assessing web sites from promotion to production.
What/How
Test links, check for platform and browser independence, and for Accessibility for individuals with disabilities. Test functionality, business rules, database connections, security of Web sites, and user interfaces of dynamic Web sites. Create a test environment that duplicates, but is separate from the production environment.
The Development Environment is used for:
- development
- developer testing
- recoding (refactoring of code), if necessary
The Development Environment does not need to duplicate the Production environment and may be combined with the Test environment.
The Test Environment duplicates the Production environment to assure accuracy of test and is used for:
- functionality testing
- performance testing
- security testing
Important Areas to Test:
- Links: Ensure every link, button, and menu choice is properly programmed.
- Platform/Browser Independence: Test for XHTML 1.0 or HTML 4.01 compliance.
- Application: Test functionality, business rules, databases, interfaces, etc.
- Performance: Test for page load time. Graphics, video and other files may affect the download time of
the page.
- Security: Conduct security tests all Web pages and Web-based applications for that access agency data.
Test for any security holes that may compromise agency Web servers and database. Provide a case code review as needed.
Checklist: Test User Environment
Resources
Related guide topics