Skip to content

Latest commit

 

History

History
25 lines (13 loc) · 1.05 KB

testing.md

File metadata and controls

25 lines (13 loc) · 1.05 KB

1. Check that passing a given input into our tests returns the expected output

2. Write tests to mimic the behaviour of a user performing different actions

The above screenshots show the first end to end test written. It mimics the behaviour of the user if they were to type in a new task (Mop the floor) in the .task-input field and click on the submit button. The js click() method was used to simulate a mouse click on the .add-task element which fired the click event. The second screenshot shows the test passing which has used helper functions to assist the console.log() being more informative for other developers.

3. Write testable, modular functions

4. Write functions that add, remove or modify DOM nodes

5. Apply event listeners to HTML form elements

6. Use scope to control what variables are accessible inside functions and blocks

7. Use CSS grid to create complex layouts

8. Use CSS grid to make layouts that adapt to the viewport size