Completed
- How do you introduce tests if you have a large project?
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Introduction to Software Testing
Automatically move to the next video in the Classroom when playback concludes
- 1 - Introduction
- 2 - Why people avoid testing
- 3 - What is testing?
- 4 - What is an assertion?
- 5 - What types of testing are there?
- 6 - Difference between the developer and the user perspective
- 7 - How much testing do I need to do?
- 8 - Congrats to Milos for getting the job!
- 9 - Is there a difference between writing tests before or after the code is developed?
- 10 - At what point does testing begin?
- 11 - Regression Testing
- 12 - What is the difference between testing and debugging?
- 13 - What are testing tools/frameworks/libraries?
- 14 - What do you think of Jest testing?
- 15 - What is security testing
- 16 - Is testing done by UX? Or can we avoid testing by utilizing UX research?
- 17 The difference between Automated and Manual testing
- 18 - Should tests be precise or flexible?
- 19 - How does the unit testing process function on a project?
- 20 - How do you introduce tests if you have a large project?
- 21 - Usability testing vs User-acceptance testing
- 22 - Cross browser testing
- 23 - Who is executing the unit testing/integration testing/regression testing?
- 24 - Are end-to-end tests different from integration tests? What are they?
- 25 - What is API testing? / Postman
- 26 - As a QA engineer, how do you test coverage?
- 27 - Is there a point at which you need to start unit testing your unit test software?
- 28 - Should you write tests for third-party APIs without mocking in case the JSON structure changes?
