Unit Notes. ICAWEB501A Build a dynamic website Topic 4 Test web application

Transcription

1 Unit Notes ICAWEB501A Build a dynamic website Topic 4 Test web application

2 Copyright, 2014 by TAFE NSW - North Coast Institute Date last saved: 10 March 2014 by Amanda Walker Version: 1.0 # of Pages = 10 Copyright of this material is reserved to the Crown in the right of the State of New South Wales. Reproduction or transmittal in whole, or in part, other than in accordance with the provisions of the Copyright Act, is prohibited without written authority of TAFE NSW - North Coast Institute. Disclaimer: In compiling the information contained within, and accessed through, this document ("Information") DET has used its best endeavours to ensure that the Information is correct and current at the time of publication but takes no responsibility for any error, omission or defect therein. To the extent permitted by law, DET and its employees, agents and consultants exclude all liability for any loss or damage (including indirect, special or consequential loss or damage) arising from the use of, or reliance on, the Information whether or not caused by any negligent act or omission. If any law prohibits the exclusion of such liability, DET limits its liability to the extent permitted by law, to the re-supply of the Information. Third party sites/links disclaimer: This document may contain website contains links to third party sites. DET is not responsible for the condition or the content of those sites as they are not under DET's control. The link(s) are provided solely for your convenience and do not indicate, expressly or impliedly, any endorsement of the site(s) or the products or services provided there. You access those sites and use their products and services solely at your own risk. Page 2 of 10

3 Table of Contents Topic 4 Introduction Test website against the requirements... 5 Activity Complete and document the design structure... 8 Agile Testing... 8 Activity Obtain client feedback and adjust web applications as appropriate... 9 Activity Check Your Understanding Page 3 of 10

4 Topic 4 Introduction This is Topic 4 of 4 topics. This topic will assist you to test your developed web application to ensure that it meets your client s requirements. In this topic, you will learn how to: Test website against the requirements Complete and document the design structure Obtain client feedback and adjust web application as appropriate Using the Unit Notes Icons and symbols are used throughout the guide to provide quick visual references. They indicate the following: Icon Meaning Icon Meaning ACTIVITY: An activity is listed to be completed ACTIVITY: A Learning activity requiring some physical action WWW: A web link is listed IMPORTANT: A pivotal point is detailed REFLECTION: A point is to be considered and thought about more deeply SEARCH: A particular item / book etc needs to be found and applied Page 4 of 10

5 4.1 Test website against the requirements These notes will serve as an introduction to the concepts associated with testing of websites. You are encouraged to do further research on testing methods as you progress with your website development, different sites will have different needs and the tools that are available change regularly. After completing this unit you will understand the concepts and be able to apply them, however be sure to customise your testing to cater for things such as your client needs, your development environment and the complexity of the solution. You have worked hard to get to this stage so testing will indicate whether you have managed to achieve all requirements for your project. Essentially, you should test your website or web application against: All major browsers such as IE, Chrome, Firefox, Safari and Opera. MAC users will generally have Safari and Chrome as their preferred ones. Most browsers have developer tools (F12 key), which allow you to simulate the previous versions of the browser but you don t want to go there. Not all versions are to be tested but only those which are still supported such as IE 8 or 9 and above. Find out more from: You need to ensure that you have implemented a test-driven development for your project. The approach is to write the test before you write the code (apart from the usual client-side validation which you do) so that you know you have the code or at least can amend the code when it fails. The goal should be 100% code coverage so each line of code will have at least a corresponding test. In this way, you can ensure that the line of code is there in response to the requirements so that the requirements are tested. A simple algorithm for the object methodology testing is such as: [TestMethod] //set the values //call the method //assert that the method returns something or throws an exception Page 5 of 10

6 Sample Application-Level Security Requirement Testing This was a snippet below was taken from Page 6 of 10

7 Access this document and read up on some important concepts in section 2. Some of the additional re-enforcement which you are familiar with are stipulated below. Having completed the website, testing it is the next stage. A website that contains dynamic content can be difficult to test. However there are some underlining methods of object testing which can be employed in your project: This is an important process as all the functionality of the website will be identified here. You will use this outcome as part of your buy-off process with your client and as basis for the adjustments needed or added enhancements which your client may seek for the website developed. There is the common Code Validation: HTML checking the background coding of the design against the HTML5 Standard (DOCTYPE declaration) the web pages are using. It also needs to meet standards compliant coding with cross browser compatibility issues addressed (IE, Chrome, Opera, Firefox and Safari). You may use this: CSS coding is checked for errors. The code validators check that the web page style sheet coding is in compliance with CSS standards set by the W3C. Alt Attribute ensure that image has an alt attribute. JavaScript Code Quality Tool: and JQuery Browser Support Website Navigation Link checking Waiting for an object check whether a page is fully loaded to make sure that all the needed object exist. Page 7 of 10

8 Activity 4.1 Considering website accessibility is important. There was some discussion of this in the earlier topics so please follow this URL and perform your accessibility checks Complete and document the design structure As mentioned previously, the test-driven development will offer you the opportunity to re-develop the SDS and even perhaps revise your Business Requirements as done earlier. You can see here the importance of what is commonly used now: Agile Technologies. This has evolved from the era of waterfall models to rapid application development of what is more so used in software engineering (Joint Application Development) and now Agile. Create a user acceptance testing document to document the results and update all document and application as necessary. Agile Testing It is software testing practice which treats the software development as the customer of testing. This means that Agile development integrates testing into the development process which is essentially what you need to achieve for this project due to your time frame constraint. So what s involved here? Testing is the integral portion of the core software development actively participates throughout the software coding process. One setback for you may seem that this practice is with team members however, this project has allowed for you to wear many hats in accomplishing the outcome needed. You are the designer, engineer, database administrator, developer, tester, documenter and project manager. How streamlined is that? Activity 4.2 Revisit at all documentation and code then proceed to retest so as to ensure that you have met all requirements for the project. Page 8 of 10

9 4.3 Obtain client feedback and adjust web applications as appropriate You have reached the day when your client will look at the work done and evaluate. You have prepared the documentation needed thus far so ensure that you also include document version control. When the project is complete it is important that the project sponsor and potentially also key stakeholders signoff the deliverables and provide feedback. Who should complete the signoff will be dependent on the project and the clients advice regarding authorised persons, typically though for a small project this would be the project sponsor and perhaps a key user. Ideally there should have been User Acceptance Testing (UAT) performed and the results of the testing reviewed with any relevant updates completed and retested. This then forms the basis for the acceptance and formal signoff. For some small projects a decision not to complete formal UAT may be made by the customer, this is not ideal however should this occur you should still seek the signoff as this is the official end of the project. It is the client who is at that point taking responsibility for confirming the solution is completed and meets the project objectives. This is an important milestone in the project and as such this should be an official document that contains details including: details to identify what is being signed off when the acceptance is occurring who is accepting the solution Page 9 of 10

10 The following is a sample taken from Activity 4.3 Research final sign-off on the Internet use the keywords template project sign-off. Look for some specific examples of sign-off sheets. Check Your Understanding I can now Test website against the requirements Complete and document the design structure Obtain client feedback and adjust web applications as appropriate Page 10 of 10