Assignment 1
Welcome to your first assignment!
Here's what you need to do:
Part 1
- Choose something you've made that is publicly accessible, or put a new page on the internet! For the simplest way to put up a page on the internet from scratch, follow these instructions on using Netlify Opens in a new window.
Really, just do whatever's easiest for you so that you can have someone test a page/feature that you wrote. Code quality is not a part of your grade for this assignment, so feel free to simply re-create a few paragraphs of content from Wikipedia, use boilerplate HTML Opens in a new window, or whatever makes this step easy for you, while still providing your partner some links and content to test. - Write up the requirements such that it could tested using our ad hoc testing tools. Include the following:
- The URL of the page being tested
- Screenshot or wireframes of the page in its intended state - including desktop, tablet & mobile
- Link URLs
- Copy (i.e. the text content of the page)
- Put this in a document (word/google doc is fine). Feel free to be informal, so long as you're thorough and understandable. Write it in such a way that your partner and I can understand it without asking you questions about it, never having seen the page being tested.
- Email this to your partner and include me on the email by cc'ing simon.borer@humber.ca by 9am Toronto time, June 1st.
Part 2
- Using our ad hoc tools, test the page for the following:
- HTML & CSS validation
- Accessibility
- JSHint errors/warnings
- Lighthouse recommendations for Performance, Best Practices, & SEO
- Dev tools security audit issues
- Responsive layout issues
- Form submission (if applicable)
- Compliance for layout and content provided by your partner
- Log any issues in a spreadsheet
- Provide all information that would be required to locate and understand the issue in order to fix it - without having to follow up with you.
- Make sure your report is readable and understandable. Again, you don't need to be formal, but you do need to be helpful.
- Submit this report, along with the original requirements document that your partner sent to you, on Blackboard by 9am Toronto time, June 8th.
You are not critiquing the page - you are testing it. If you don't like the information architecture, or colour palette, but it doesn't throw any errors - that's not an issue for your report.
You can ignore any validation errors generated by 3rd-party libraries (CSS, JS, etc.) like jQuery, tailwind, or what have you.
You're not actually going to have to fix any issues. Ignoring or downplaying issues won't make your partner look good, and it won't save your partner any labour.