Flashcards v3
Test Plan and Test Cases
• A formal test strategy is necessary, since it may be followed by different testers when the media has been implemented. • Next, define, document and justify a test plan containing appropriate and comprehensive test cases - Prepare sample data appropriate for each of the defined test cases, also include abnormal data. - Record the expected result for each test case and data set Explanation of Terms used • Test Strategy - A formal method that allows for the well-ordered testing of the media. • Test Plan - A structured and methodical plan of attack. • Test Case - A description of what is going to be tested. • Test Data - The specific data that will be used in the test. • Expected Results - What the interactive media should do. • Actual Results - What the interactive media actually does.
Design a Storyboard
• A storyboard describes in detail the layout and content of interactive media pages. • A storyboard gives a developer concise and visual information regarding each page of a site. This information may include: - the style sheet to use, - background image, - other resources, - links etc.
Determine Goals / Objectives and Identify Requirements
Analyse the project brief to: Establish Goals and Objectives Identify functional requirements Identify non-functional requirements Verify the specification Deliverable = Software Requirements Specification
Things to include in your Evaluation
1. Accessibility • a Browser (Internet Explorer, Firefox, Netscape Navigator, Safari, Konqueror) • b Platform (Windows, Linux, Macintosh) • c Flash Player (various versions of the player) • d Users with special needs (e.g. visual impermanent — font size, colour adjustments, use of alert sounds, screen reader) • e Language 2. Ease of use a Navigation b Information c Context 3. Aesthetics • a Design • b Layout • c Colour scheme • d Fonts • Deliverable = Evaluation report
Establish Goals
Establish top level strategic goal(s) - Goals are long term (general) Establish SMART objectives Objectives are short/medium term statements,and must be clearly outlined with timelines, budgets, and personnel needs e.g. I want to create a contact page with company address, telephone and email link; I want to create WebPages that a user can vary text size Develop a clear vision of the target audience using suitable classifications e.g. • By age group By social group By education level • By interests By expectations By accessibility requirements • By interaction By context of use By hardware/software • By support By feedback by IT skills • By restrictions or limitations in time, resources, By knowledge/skills
Step 3: Determine how to Test the product
The aim of testing is to ensure that a solution is robust, satisfies the functional requirements and can be considered fit for purpose The test strategy requires you to select and justify two or more test strategy methods to be used in the testing of a solution e.g. - Usability Testing - A properly executed usability test of your multimedia package or Web site can reveal answers to whatever you design the test to ask. However, in most cases it will uncover three key things: Areas of confusing navigation, Users' intuitive viewing sequences, Blocks in the flow or delivery of information - User Observation Testing - Users are given a set of tasks to complete. The users are observed / video taped interacting with the Web site to pinpoint specific usability problems - Think Aloud Protocol - participants think aloud as they are performing a set of specified tasks. Test sessions are often audio and video taped so that developers can analyse the user's actions later - User Acceptance Testing - Usually performed by clients or end-users (customer) prior to accepting transfer of ownership. Test scenarios may have one or many acceptance tests, whatever it takes to ensure the functionality works. Acceptance tests are black box system tests. Test Plan and Test Cases
List of Non-Functional characteristics
Type of test Test definition Accessibility =Verify the ability to access the functionality of the application. Audit and control= Verify how easily it's possible to check the historic workflow and audit trail. Availability= Verify that the application has a high uptime as stipulated in the service level agreement (SLA). Compatibility= Verify if the application fits in a pre-existing (older) environment. Documentation =Verify that the user guides provide the right instructions. Installation=Verify if the application works on the defined middle ware stack. Interoperability= Verify if application works after changing a vital component in the environment. Load/Volume= Verify if the application processes the required number of transactions in a given time. Maintainability=Verify how easy it is to maintain the application after it goes into production. Performance=Verify if criteria like response time, throughput, concurrency and so on meet requirements. Reliability =Verify that the application works if stressed in production-like environment. Scalability =Verify if the application can meet the growing needs of a business. Security= Verify if the application has enough security to protect information theft. Serviceability= Verify if the application can be debugged without making any impact on the business. Usability= Verify that the application is usable from an end-user perspective.
Verify the specification
Verify the specification Verification can be viewed as double-checking that all requirements have been addressed and are listed in the document Verification takes the form of examining the project brief and the requirements listed in the requirement specification and crossing off each. If there are six functional requirements and five non-functional requirements in the requirements specification document, then there should be six and five respectively in the project brief Deliverable = Software Requirements Specification
Design Considerations
• Cascading style sheets: A style sheet is a way of separating the structure and content from the visual style and layout of a web page. An external style sheet will assist in meeting design decisions, such as repetition of heading styles, etc. • Interaction style: The interaction styles that are to be used in the completed media must be decided on during the design stage, e.g. keyboard, mouse, icon and menu. The navigation style must also be chosen, e.g. buttons, menus, images. • Media acquisition: During the design stage it must be decided where the different elements of the interactive media product are going to be sourced. It may be the case that many of the items, e.g. photographs, can be provided by the client, however, there may be other items that have to be created from new or acquired from a third party • Copyright: Although internet-based content is freely available, the actual content itself is not necessarily free. Copyright applies, so if a developer wishes to utilise a copyrighted resource then the copyright owner must be contacted and permission sought. • Colour safe: It is always a good idea to investigate the use of safe colours when designing an interactive media product. The reason for this is that developers tend to have better equipment than users, and something that looks good on the developer's system may not look so good on the users system.
Step 4: Determine how to Evaluate the Product
• Evaluation is the process used to determine that a completed product satisfies the given brief and the subsequent analysis. • It also determines whether the product is fit for purpose. Elements that will be evaluated will be - accessibility - usability - aesthetics • Evaluative data is often gathered from users. Evaluation will only be successful if it is specific, balanced, honest and solution oriented. • There are many different questions to be asked and answered during evaluation and every interactive media product requires its own unique evaluation.
Fact finding (Analysis)
• Fact finding - Gather and analyse information (what, why, where, when, who) from client using various techniques (face-to-face interviews, questionnaires, observation, examining system documentation) - Deliverable = Project Brief
Evaluation Questions
• For user evaluation testing, it must be made clear that the user realises it is the interactive media that is being evaluated and not them. The user should be told that there is no right or wrong way to use the product. Evaluators should be asked to be frank and open with their opinions on the product. • Typical questions that can be part of an evaluation include: - Is the web site performing poorly in search engines? - Does the web site conform to Government regulations, e.g. the Disability Discrimination Act (DDA)? - Does the web site give a return on its investment? - Is the look of the site adequate? - Is the navigation easy to use? - Is the content satisfactory? - Is the target audience catered for? - Is the content is up to date and fit for purpose?
Features of Functional Requirements
• Functional requirements should document "what a system should do" and not how it does it. • The described behaviour may come from organisational or business rules, or it may be discovered through the requirements discovery process. • Functional requirements must be clear, correct, unambiguous, specific, and verifiable.
Identify functional requirements
• Identify functional requirements - User/system requirements of what a solution must do e.g.to use text and images to provide an educational resource; to allow a user to navigate a web site using a mouse or keyboard; to provide user with the ability to vary text size
non-functional requirements
• Identify non-functional requirements - Constraints on the development of the interactive media product, e.g. the budget allocated to the development; the time scale it must be completed in; the quality/standards it should follow; the legal acts it must must comply with - Also include all of the other elements that have to be taken into consideration about an interactive media product, e.g. the audience that it is aimed at; the age range of the audience
Why are Functional and Non- Functional Requirements important
• It is important to correctly classify requirements as functional or non-functional as doing so helps to ensure that the system meets all of the needed business requirements.
Features of Non-Functional Requirements
• Nonfunctional requirements (NFRs) describe additional constraints on what constitutes an acceptable software solution • How well the system should perform its functions
Design a Site Map
• Site maps are ideal for showing the overall structure of an interactive media product. • The description of each rectangle in a site map should use one or two key words, typically verb and noun, e.g. contact us, which will explain instantly what the function / purpose of the particular page is. • The design documentation should also include textual narrative stating in words the function of each page that is referenced to the site map.
Storyboards/ Navigation Maps
• Storyboards give a visual representation of what the screen layout will look like. It contains information on the colour schemes, typography schemes, layout of elements and media elements. • Navigation maps give a representation of the logical structure of the application. They show how the different screens connect to each other. They also give an indication of the size of the application being produced. • Deliverable = Design Specification
Things to include in your Test Plan
• Technical Testing: test on a range of equipment and platforms • Browser Testing: test on the most popular browsers • Visual Testing: test that the media has followed the major design principles of contrast, repetition, alignment and proximity (CRAP) • Platform Testing: test various platforms (hardware and software), i.e. a computer and the operating system • Bandwidth Testing: Tools are available for this • Download Speed Testing: Tools are available for this • Compatibility Testing: Test different browsers and operating systems • Usability Testing: should help answer the question of does the interactive media have a consistent feel, e.g. navigation, and layout • Accessibility Testing: Tools are available for this • Forms Testing: Forms should be tested to make sure that they are usable and that they can be completed using the keyboard only, if necessary • Data Table Testing: Test for accessibility issues with tables • W3C Compliance Testing: test web site for compliance to W3C's recommendations and standards concerning HTML and XHTML • Deliverables = Test Strategy and Test Plan
Step 2: Design the Product
• The design stage involves the answering of "How" the interactive media product will be developed to meet the necessary requirements. • There are four major design considerations that need to be looked at when designing an interactive media product: - Contrast Repetition Alignment Proximity - C.R.A.P. • During the design stage other considerations must be formalised and planned. Typical items that have to be thought about and decisions made upon are: - Cascading Style Sheets Interaction styles Media Acquisition Copyright Colour Safe
