Assignment 7 Instructions

General Instructions for your Assignments:

During Week 1 through Week 7 of this course, you will have a new assignment each week. You should create a new set of files for each assignment. During Weeks 1 through 7 you are NOT building on your previous assignment, like you did in WEBD121. Instead you are creating a new set of files for each assignment. However, make sure you save all of your files from each assignment because you will need them later for your Final Project. During Week 8, for your Final Project, you will create a Home Page with a navigation menu that uses JavaScript for drop-down sub-menus, which will link all of your previous assignments together, creating a comprehensive website that showcases all of your work this semester.

You must write the code files by hand for all assignments in this class. A simple text editor, such as Notepad or Notepad++ will suffice (or TextEdit on the Mac). DO NOT use GUI editors, such as FrontPage, Dreamweaver, etc. You must write the code for your web page files yourself. If you are using a PC, it is strongly recommended that you download the free Notepad++ text editor because it contains extra features which assist with debugging, such as line numbering and color coding of different elements of syntax. Mac users should use the TextEdit text editor that comes with the Mac OS. However, if you are a Mac user, make sure you set TextEdit to use Plain Text by default.

Make sure all of your web pages comply with the HTML 5 standards and CSS standards. DO NOT use obsolete HTML elements and attributes from previous versions of HTML. By including the HTML 5 DOCTYPE declaration in your webpages, and validating all of your HTML files, you can be sure that your code complies with HTML 5. Also, make sure that your external style sheet (.css file) passes validation at the W3C CSS Validation Service. Make sure you use the “Validate by File Upload” option (and NOT the “Validate by Direct Input” option), on both of these validators since this is the way your instructor will check your pages when grading your assignments.

Specific Instructions for Assignment 7:

Perform all of the following steps to complete this assignment:

1) Begin by creating a new file in your text editor and include all of the basic HTML code like you did in your previous assignments. Or you can simply make a copy of your HTML file from last week and name the new copy LastFirstAssignment7.html (where “Last” is your last name and “First” is your first name), but be careful not to overwrite your file from last week because you will need it again when you do your Final Project during Week 8.

2) Make sure you change the contents of the <title> tag to “Assignment 7” (just the words – not the quotation marks) and make sure your full name is inside of the <h1> heading, just like in your previous assignments. Also, delete the contents of the <script> tag — everything between the <!– and //–> tags, if you created your new file by making a copy of your previous file, because you will be creating a brand new page with different JavaScript code for this assignment. Save your file.

3) Upload this file to the HTML validator to check for compliance with the HTML5 standards. Your file should pass validation. If you receive any errors or warnings, then go back through the previous steps of the assignment again until you have corrected all errors and your file passes validation.

4) Create another new file in your text editor and save it as Assignment7.css or make a copy of last week’s CSS file, being careful not to overwrite last week’s file.

5) In your CSS file, write code to set the background color of your page to #FFB3B3 and write code to center the h1 element. Save your CSS file.

6) Access your webpage again in your browser and confirm that your page has a pale red background and that the heading is centered. Upload your CSS file to the CSS validator to check for compliance with the CSS standards. Your file should pass validation. If you receive any errors or warnings, debug your CSS code until you have corrected all errors and your file passes validation.

7) Open your Assignment 7 HTML file for editing. Next, you will reuse and slightly modify code from Lab 11-4. Make sure you change the value of “expires” to a future date. Similar to Lab 11-4, prompt the user to enter a hexidecimal color code. However, instead of prompting them for their name, prompt them to enter their age. Your code should set a cookie with the information the user enters and then retrieve that information from the cookie and set the page background to the color entered by the user.

Note: It is recommended that you test this assignment in Internet Explorer and/or Firefox. This code may not work correctly in Chrome.

8) You may add any additional HTML, CSS, or JavaScript content that you wish, to practice more of the features that you have learned about in your online textbook, as long as all of your code files still pass validation. However, do not add anything to your files that would make them invalid according to the standards. You can confirm this by making sure your files still pass validation.

9) Before submitting your assignment, validate your HTML and CSS files one last time at Validation Service AND W3C, using the “Validate by File Upload” option. Note: It is critical that you debug and fix ALL errors identified by the validator before submitting your assignments. Contact your instructor for assistance if you are having difficulty debugging and fixing your errors because it is imperative that all of your code files pass validation.

10) Create a zip archive containing all pages pertaining to your website (.html files, .css files, .js files, image files, etc). Make sure you maintain the necessary directory structure in your zip archive so that your webpages will refer correctly when unzipped. In other words, if your images are in a sub-folder, in relation to the folder containing your .html file, then you need to maintain that same directory structure in your zip archive, too, including the sub-folder. Submit only the zip file for grading.

Validation Requirements:

Before submitting your web site:

1. Validate your HTML file at W3C, using the “Validate by File Upload” option, and fix any errors that the validator identifies before submitting your web site for grading.
2. Validate your CSS file, using the “Validate by File Upload” option, and fix any errors that the validator identifies before submitting your web site for grading.

Note: It is critical that you debug and fix ALL errors identified by these two code validators before submitting your assignments. Contact your instructor for assistance if you are having difficulty debugging and fixing your errors because it is imperative that your code files pass validation. Remember that valid JavaScript relies on a foundation of valid HTML and valid CSS to function as intended.

Submission Instructions: Create a zip file containing all files related to your web page (.html files, .css files, .js files, image files, etc). Make sure you maintain the necessary directory structure in your zip file so that your webpages will access correctly when unzipped. In other words, if your images are in a sub-folder on your computer, in relation to the folder containing your .html file, then you need to maintain that same directory structure in your zip file, too. Submit only the zip file for grading.

• When do we start testing and what are the different types of testing that can be performed?,

• From your Design Specification please post an image of one or more of the following: architecture diagram application class diagram detailed class diagram test cases and scenario persistent class diagram with SQL statements or sample Java statements in the Design Peer Review,

• Provide a brief discussion of its contents,

• Explain how it meets the requirements in the IT Online Requirement specification,

• Identify any features you like or issues you encountered,

Software Testing Discussion

Discussion Points

• Part I.  When do we start testing and what are the different types of testing that can be performed?  A web search for relevant articles and information could be employed to assist you in your response.
• Part II. Design Peer Review – From your Design Specification, please post an image of one or more of the following: architecture diagram, application class diagram, detailed class diagram, test cases and scenario,  persistent class diagram with SQL statements, or sample Java statements in the Design Peer Review with a brief discussion of its contents, how it meets the requirements in the IT Online Requirement specification, and any features you like or issues you encountered.  An image is easier for everyone to access.
• 

  • When do we start testing and what are the different types of testing that can be performed?,

  • From your Design Specification please post an image of one or more of the following: architecture diagram application class diagram detailed class diagram test cases and scenario persistent class diagram with SQL statements or sample Java statements in the Design Peer Review with a brief discussion of its contents, how it meets the requirements in the IT Online Requirement specification and any features you like or issues you encountered.

    ---

    Comprehensive Response

    Part I: When to Start Testing & Types of Testing

    When Testing Should Begin (“Shift-Left” Approach)

    Testing should begin as early as possible in the software development lifecycle — ideally even before any code is written. This concept is known as shift-left testing, which means moving testing activities “left” on the project timeline. By integrating testing into the early phases (like during requirements and design), teams can identify defects early, reduce cost, and improve quality. Wikipedia+1

    Early testing also includes writing acceptance test criteria during the requirements/design phase. For example, in development models like the V-Model, test planning and test specification happen in parallel with design. درجات

    During coding, unit tests by developers (often automated) validate individual components. Then, as modules are combined, integration testing ensures that the different parts interact correctly. geeksforgeeks.org+2Atlassian+2

    Types of Testing

    There are many types of software testing, each serving a specific purpose:

    1. Unit Testing

       • Tests individual functions, methods, or classes in isolation. geeksforgeeks.org+1

       • Generally performed by developers, often automated (e.g., JUnit). Atlassian

    2. Integration Testing

       • Tests how multiple units or modules work together. geeksforgeeks.org

       • Helps catch issues in data flow, APIs, or module interactions. Wikipedia+1

    3. System Testing

       • Validates the complete, integrated system to ensure it meets the specified requirements. DesignRush+1

       • Can involve functional and non-functional tests (performance, security, etc.). International Software Test Institute

    4. Acceptance Testing (User Acceptance Testing)

       • Formal testing that verifies the system meets business requirements. DesignRush+1

       • Often done by stakeholders or end users. Global App Testing

    5. Smoke / Sanity Testing

       • Preliminary tests to check basic functionality or build stability before deeper testing. TestDevLab

       • Smoke testing helps decide whether a build is stable enough to proceed with more complete testing. Wikipedia

    6. Regression Testing

       • Repeated testing of existing functionality to ensure new changes haven’t broken anything. Global App Testing

    7. Exploratory and Ad-Hoc Testing

       • Informal testing without predefined test cases; relies on tester intuition to find edge-case bugs. TestDevLab

    8. Non-functional Testing

       • Tests aspects such as performance (load, stress), security, usability, and compatibility. gwcet.ac.in

    By combining these different testing types throughout the development process, teams can ensure robustness, usability, performance, and compliance with business requirements.