1 / 32

Testing and delivery

Testing and delivery. Web design principles. Web development is software development. Web sites are client/server applications. Like any software development project testing and managed delivery is essential. The ‘testing cycle’ can be distilled down to simple steps. Functionality Testing

chill
Download Presentation

Testing and delivery

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Testing and delivery Web design principles

  2. Web development is software development

  3. Web sites are client/server applications.

  4. Like any software development project testing and managed delivery is essential.

  5. The ‘testing cycle’ can be distilled down to simple steps

  6. Functionality Testing Usability testing Interface testing Compatibility testing Performance testing Security testing

  7. If your application fails at any step the problem must be fixed and the application put back through the test cycle until it is clear at every step

  8. To test something we need to start with an idea of what it’s actually supposed to be or do

  9. Starting with a design or specification is the simplest way to test what you build

  10. Defining ‘success criteria’ will allow you to know whether you did a good job or even if you are actually finished !

  11. Your initial design & spec should have answered some or all of these questions

  12. Who is the target audience? • What kind of browsers will they be using? • What kind of connection speeds will they be using? • Which HTML specification will be adhered to? • What variations will be allowed for targeted browsers? • What are the standards for page appearance and graphics throughout the site ? • How will internal and external links be validated and updated?

  13. Before beginning testing some questions about HOW you will do testing need to be answered.

  14. Think about how you test Can testing be done on the production system, or is a separate test system required? How are browser caching, option settings, connection differences and real-world problems accounted for ?

  15. Functionality Testing:

  16. Check all the links • Test the outgoing links from all the pages from specific domain under test. • Test all internal links. • Test links jumping on the same pages. • Test links used to send the email to admin or other users from web pages. • Test for orphan pages. • Test for broken links in all the above

  17. Test forms in all pages • Test all the validations on each field. • Test for the default values of fields. • Test for wrong inputs to all form fields • Test options to create, delete, view or modify the forms.

  18. Validate your HTML/CSS Test ALL your pages against the specified standard. Validate your HTML Validate your CSS Check if your site is indexable in search engines.

  19. Usability Testing

  20. Test for navigation Test to ensure a user can move from one page to another. Test to see if your site is easy to use. Provide clear, relevant, CORRECT instructions Provide consistent menu and navigation elements on each page

  21. Content checking: Content should be logical and easy to understand

  22. Check for spelling errors.

  23. Check again for spelling errors.

  24. Remember It is almost impossible to accurately proof read material you have written yourself.

  25. Compatibility Testing

  26. Test browser compatibility Test Operating system compatibility Test Mobile browsing compatibility Test Printing options

  27. Final Delivery

  28. Install your site in the actual domain in a methodical fashion.

  29. Test it all again.

  30. Yes, actually test it…

  31. Manage the handover to the client Get sign off Deliver access codes, documentation and keys

  32. http://www.softwaretestinghelp.com/how-can-a-web-site-be-tested/http://www.softwaretestinghelp.com/how-can-a-web-site-be-tested/ http://pingmag.jp/2005/12/09/the-website-development-process/ http://www.websiteoptimization.com/services/analyze/ http://www.linktiger.com/index.jsp http://articles.sitepoint.com/article/ultimate-testing-checklist#

More Related