JavaScript Testing Best Practices

Best Practices of Unit Testing 6 lectures 26:15 The Course Overview This video will give you an overview about the course. Write Great Test Names Test names should be descriptive of what they do. • Use describe • Use expect Single Responsibility Principle According to the single responsibility principle, methods should do one thing. • Move functionality to separate methods • Express the single responsibility principle in your tests Covering All Test Cases Test coverage is very important. To achieve the best test coverage, we need to carefully examine every part of the code base. • Follow a step by step approach • Make sure that all errors are covered • Errors that never happen in a code flow should not be checked Improving Your Tests with a Linter Using a linter makes sure we use the same style in all test files. • Install eslint • Use a template • Lint the test files Handling and Expecting Errors Errors should be handled first and we should use assert to expect our methods to throw errors. • Replace try/catch with assert • Move checks for errors to the top of the file Best Practices of Unit Testing - Quiz Best Practices of Unit Testing 6 lectures 26:15 The Course Overview This video will give you an overview about the course. Write Great Test Names Test names should be descriptive of what they do. • Use describe • Use expect Single Responsibility Principle According to the single responsibility principle, methods should do one thing. • Move functionality to separate methods • Express the single responsibility principle in your tests Covering All Test Cases Test coverage is very important. To achieve the best test coverage, we need to carefully examine every part of the code base. • Follow a step by step approach • Make sure that all errors are covered • Errors that never happen in a code flow should not be checked Improving Your Tests with a Linter Using a linter makes sure we use the same style in all test files. • Install eslint • Use a template • Lint the test files Handling and Expecting Errors Errors should be handled first and we should use assert to expect our methods to throw errors. • Replace try/catch with assert • Move checks for errors to the top of the file Best Practices of Unit Testing - Quiz The Course Overview This video will give you an overview about the course. The Course Overview This video will give you an overview about the course. The Course Overview This video will give you an overview about the course. The Course Overview This video will give you an overview about the course. This video will give you an overview about the course. This video will give you an overview about the course. Write Great Test Names Test names should be descriptive of what they do. • Use describe • Use expect Write Great Test Names Test names should be descriptive of what they do. • Use describe • Use expect Write Great Test Names Test names should be descriptive of what they do. • Use describe • Use expect Write Great Test Names Test names should be descriptive of what they do. • Use describe • Use expect Test names should be descriptive of what they do. • Use describe • Use expect Test names should be descriptive of what they do. • Use describe • Use expect Single Responsibility Principle According to the single responsibility principle, methods should do one thing. • Move functionality to separate methods • Express the single responsibility principle in your tests Single Responsibility Principle According to the single responsibility principle, methods should do one thing. • Move functionality to separate methods • Express the single responsibility principle in your tests Single Responsibility Principle According to the single responsibility principle, methods should do one thing. • Move functionality to separate methods • Express the single responsibility principle in your tests Single Responsibility Principle According to the single responsibility principle, methods should do one thing. • Move functionality to separate methods • Express the single responsibility principle in your tests According to the single responsibility principle, methods should do one thing. • Move functionality to separate methods • Express the single responsibility principle in your tests According to the single responsibility principle, methods should do one thing. • Move functionality to separate methods • Express the single responsibility principle in your tests Covering All Test Cases Test coverage is very important. To achieve the best test coverage, we need to carefully examine every part of the code base. • Follow a step by step approach • Make sure that all errors are covered • Errors that never happen in a code flow should not be checked Covering All Test Cases Test coverage is very important. To achieve the best test coverage, we need to carefully examine every part of the code base. • Follow a step by step approach • Make sure that all errors are covered • Errors that never happen in a code flow should not be checked Covering All Test Cases Test coverage is very important. To achieve the best test coverage, we need to carefully examine every part of the code base. • Follow a step by step approach • Make sure that all errors are covered • Errors that never happen in a code flow should not be checked Covering All Test Cases Test coverage is very important. To achieve the best test coverage, we need to carefully examine every part of the code base. • Follow a step by step approach • Make sure that all errors are covered • Errors that never happen in a code flow should not be checked Test coverage is very important. To achieve the best test coverage, we need to carefully examine every part of the code base. • Follow a step by step approach • Make sure that all errors are covered • Errors that never happen in a code flow should not be checked Test coverage is very important. To achieve the best test coverage, we need to carefully examine every part of the code base. • Follow a step by step approach • Make sure that all errors are covered • Errors that never happen in a code flow should not be checked Improving Your Tests with a Linter Using a linter makes sure we use the same style in all test files. • Install eslint • Use a template • Lint the test files Improving Your Tests with a Linter Using a linter makes sure we use the same style in all test files. • Install eslint • Use a template • Lint the test files Improving Your Tests with a Linter Using a linter makes sure we use the same style in all test files. • Install eslint • Use a template • Lint the test files Improving Your Tests with a Linter Using a linter makes sure we use the same style in all test files. • Install eslint • Use a template • Lint the test files Using a linter makes sure we use the same style in all test files. • Install eslint • Use a template • Lint the test files Using a linter makes sure we use the same style in all test files. • Install eslint • Use a template • Lint the test files Handling and Expecting Errors Errors should be handled first and we should use assert to expect our methods to throw errors. • Replace try/catch with assert • Move checks for errors to the top of the file Handling and Expecting Errors Errors should be handled first and we should use assert to expect our methods to throw errors. • Replace try/catch with assert • Move checks for errors to the top of the file Handling and Expecting Errors Errors should be handled first and we should use assert to expect our methods to throw errors. • Replace try/catch with assert • Move checks for errors to the top of the file Handling and Expecting Errors Errors should be handled first and we should use assert to expect our methods to throw errors. • Replace try/catch with assert • Move checks for errors to the top of the file Errors should be handled first and we should use assert to expect our methods to throw errors. • Replace try/catch with assert • Move checks for errors to the top of the file Errors should be handled first and we should use assert to expect our methods to throw errors. • Replace try/catch with assert • Move checks for errors to the top of the file Best Practices of Unit Testing - Quiz Best Practices of Unit Testing - Quiz Best Practices of Unit Testing - Quiz Best Practices of Unit Testing - Quiz BDD Best Practices 5 lectures 27:13 Red. Green. Refactor Tests should be re-written after they fail. • Write tests without implementations • Run the tests • Build the resizer until the tests run Describing User Behavior In behavior driven development, we use describe statements to describe how our program should behave. • Use descriptive language in test names • Use describe / It Testing Only the Public API Private checks should not be tested. We should see our SUT as a black box. • Ignore private methods • Do not check for errors, that will not be exposed via the public API Using Realistic Input We need to check all possible user inputs that can cause an error. • Use undefined as a filename • Use an invalid file type Writing Plain Language Tests Cucumber allows us to write tests in plain language like English. But we have to define step definitions first. • Initialize Cucumber • Create a step definition • Write and run a feature test BDD Best Practices - Quiz BDD Best Practices. 5 lectures 27:13 Red. Green. Refactor Tests should be re-written after they fail. • Write tests without implementations • Run the tests • Build the resizer until the tests run Describing User Behavior In behavior driven development, we use describe statements to describe how our program should behave. • Use descriptive language in test names • Use describe / It Testing Only the Public API Private checks should not be tested. We should see our SUT as a black box. • Ignore private methods • Do not check for errors, that will not be exposed via the public API Using Realistic Input We need to check all possible user inputs that can cause an error. • Use undefined as a filename • Use an invalid file type Writing Plain Language Tests Cucumber allows us to write tests in plain language like English. But we have to define step definitions first. • Initialize Cucumber • Create a step definition • Write and run a feature test BDD Best Practices - Quiz Red. Green. Refactor Tests should be re-written after they fail. • Write tests without implementations • Run the tests • Build the resizer until the tests run Red. Green. Refactor Tests should be re-written after they fail. • Write tests without implementations • Run the tests • Build the resizer until the tests run Red. Green. Refactor Tests should be re-written after they fail. • Write tests without implementations • Run the tests • Build the resizer until the tests run Red. Green. Refactor Tests should be re-written after they fail. • Write tests without implementations • Run the tests • Build the resizer until the tests run Tests should be re-written after they fail. • Write tests without implementations • Run the tests • Build the resizer until the tests run Tests should be re-written after they fail. • Write tests without implementations • Run the tests • Build the resizer until the tests run Describing User Behavior In behavior driven development, we use describe statements to describe how our program should behave. • Use descriptive language in test names • Use describe / It Describing User Behavior In behavior driven development, we use describe statements to describe how our program should behave smells and avoid errors. • Download sonarqube • Download sonar scanner • Generate a...