mirror of
https://github.com/freeCodeCamp/freeCodeCamp.git
synced 2026-05-28 18:26:54 +00:00
chore(curriculum): rm vids from diff. types of testing lectures (#61572)
This commit is contained in:
hbar1st
+1
-8
@@ -1,19 +1,12 @@
|
||||
---
|
||||
id: 67d1d844d84c8b540297bbe4
|
||||
title: What Is the Overall Purpose of Testing Your Applications?
|
||||
challengeType: 11
|
||||
videoId: 2-xZcGyeJCc
|
||||
challengeType: 19
|
||||
dashedName: what-is-the-overall-purpose-of-testing-your-applications
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video or read the transcript and answer the questions below.
|
||||
|
||||
# --transcript--
|
||||
|
||||
What is the overall purpose of testing your applications?
|
||||
|
||||
Up until this point, you have been building tons of small projects in languages like HTML, CSS, JavaScript, and more. But how do you know if your projects are working correctly?
|
||||
|
||||
One option is to do what is called manual testing. This is where a tester will go through each part of the application and test out all of the different features to make sure it works correctly. If any bugs are uncovered in the testing process, the tester will report those bugs back to the software team so they can be fixed.
|
||||
|
||||
+1
-8
@@ -1,19 +1,12 @@
|
||||
---
|
||||
id: 67d2ff1996e4ae9e67170502
|
||||
title: What Is Unit Testing?
|
||||
challengeType: 11
|
||||
videoId: 1CU5baDu98U
|
||||
challengeType: 19
|
||||
dashedName: what-is-unit-testing
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video or read the transcript and answer the questions below.
|
||||
|
||||
# --transcript--
|
||||
|
||||
What is unit testing?
|
||||
|
||||
As you design your applications, you will often have a series of small functions responsible for one thing. This is known as the "single responsibility principle." When you have a series of small functions, it is best to test these functions to ensure that everything works as expected. In this lecture, we will take a look at how to create a unit test using the popular Jest testing framework.
|
||||
|
||||
In this example, we are going to create a function that is responsible for returning a newly formatted string:
|
||||
|
||||
+12
-19
@@ -1,20 +1,13 @@
|
||||
---
|
||||
id: 67d2ff33452ce69ea169c872
|
||||
title: What Is Functional Testing, and How Does It Differ from Unit Testing?
|
||||
challengeType: 11
|
||||
videoId: bmYxrOqrAfo
|
||||
challengeType: 19
|
||||
dashedName: what-is-functional-testing-and-how-does-it-differ-from-unit-testing
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video or read the transcript and answer the questions below.
|
||||
|
||||
# --transcript--
|
||||
|
||||
What is functional testing, and how does it differ from unit testing?
|
||||
|
||||
In prior lecture videos, you learned how to test small units of code through unit testing. Well, unit testing is part of functional testing. Functional testing checks if the features and functions of the application work as expected.
|
||||
In prior lectures, you learned how to test small units of code through unit testing. Well, unit testing is part of functional testing. Functional testing checks if the features and functions of the application work as expected.
|
||||
|
||||
In this lecture, we will take a look at the differences between functional and non-functional testing.
|
||||
|
||||
@@ -24,7 +17,7 @@ In contrast, non-functional testing focuses on things like performance and relia
|
||||
|
||||
A real test scenario for functional testing would be a user login. A user should be able to log in to the application with their username and password. If successful, they should be able to access their account information. If there is an issue, then that error needs to be handled properly. When you are writing tests, you need to account for all types of success and failure scenarios.
|
||||
|
||||
An example of non-functional testing would be to test the performance of your application under different network conditions. In a future lecture video, you will learn more about performance testing.
|
||||
An example of non-functional testing would be to test the performance of your application under different network conditions. In a future lecture, you will learn more about performance testing.
|
||||
|
||||
The reasons why functional testing is so important is because you want to identify bugs early on in your application. You also want to make sure that your application meets the requirements that were laid out at the beginning of the planning phase. Lastly, you want to ensure that your users have a good user experience. Users should not struggle to use your application or be blocked by broken features and system failures.
|
||||
|
||||
@@ -40,7 +33,7 @@ This tests for accessibility issues only and ensures there is 100% test coverage
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -48,7 +41,7 @@ This tests for performance issues and ensures the application performance is str
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -60,7 +53,7 @@ This tests for CSS issues only and ensures there is 100% test coverage.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
@@ -76,7 +69,7 @@ Testing the CSS of your application to make sure the styles look correct.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -84,7 +77,7 @@ Testing the HTML of your application to ensure there are no bugs.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -92,7 +85,7 @@ Testing the JavaScript files in your application to ensure they only use arrow f
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -112,7 +105,7 @@ Agile testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -120,7 +113,7 @@ Regex testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -132,7 +125,7 @@ Class testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
|
||||
+10
-17
@@ -1,19 +1,12 @@
|
||||
---
|
||||
id: 67d2ff4231359d9f21d1437a
|
||||
title: What Is End-to-End Testing?
|
||||
challengeType: 11
|
||||
videoId: km_FKnbbdf8
|
||||
challengeType: 19
|
||||
dashedName: what-is-end-to-end-testing
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video or read the transcript and answer the questions below.
|
||||
|
||||
# --transcript--
|
||||
|
||||
What is end-to-end testing?
|
||||
|
||||
End-to-end testing, or E2E for short, tests real-world scenarios from the user's perspective. Examples of E2E testing scenarios include testing the registration and login process or testing the checkout for an e-commerce site.
|
||||
|
||||
To better understand how end-to-end testing works, let's take a look at a real-world example from the freeCodeCamp codebase. This example uses Playwright, a popular end-to-end testing framework developed by Microsoft.
|
||||
@@ -86,7 +79,7 @@ Cypress
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -94,7 +87,7 @@ Selenium
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -106,7 +99,7 @@ Puppeteer
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
@@ -126,7 +119,7 @@ Java
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -134,7 +127,7 @@ Angular
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -142,7 +135,7 @@ JUnit
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
@@ -158,7 +151,7 @@ Testing the validity of CSS code.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -166,7 +159,7 @@ Testing the performance for an application.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -174,7 +167,7 @@ Testing the validity of HTML code.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
|
||||
+10
-17
@@ -1,19 +1,12 @@
|
||||
---
|
||||
id: 67d2ff5f14f6ce9f6d3cbe22
|
||||
title: What Is Usability Testing, and What Does the Process Look Like?
|
||||
challengeType: 11
|
||||
videoId: hznW5PYT5r0
|
||||
challengeType: 19
|
||||
dashedName: what-is-usability-testing-and-what-does-the-process-look-like
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video or read the transcript and answer the questions below.
|
||||
|
||||
# --transcript--
|
||||
|
||||
What is usability testing and what does the process look like?
|
||||
|
||||
Usability testing is when you have real users interacting with the application to discover if there are any design, user experience, or functionality issues in the app. This type of testing is important because this feedback will help ensure that the application meets the needs of the users.
|
||||
|
||||
The four common types of usability testing are explorative, comparative, assessment and validation testing.
|
||||
@@ -52,7 +45,7 @@ Comparative testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the lecture video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -64,7 +57,7 @@ Validation testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the lecture video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -72,7 +65,7 @@ Explorative testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the lecture video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
@@ -92,7 +85,7 @@ JUnit
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the lecture video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -100,7 +93,7 @@ Jest
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the lecture video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -108,7 +101,7 @@ Mocha
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the lecture video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
@@ -124,7 +117,7 @@ Usability testing focuses on performance issues in the application, while functi
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the lecture video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -136,7 +129,7 @@ Usability testing focuses on the functionality of the application, while functio
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the lecture video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -144,7 +137,7 @@ Functional testing focuses on accessibility issues, while usability testing focu
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the lecture video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
|
||||
+4
-11
@@ -1,19 +1,12 @@
|
||||
---
|
||||
id: 67d2ff6f069dce9feacb7d25
|
||||
title: What Is Compatibility Testing?
|
||||
challengeType: 11
|
||||
videoId: 583-W-c4WNI
|
||||
challengeType: 19
|
||||
dashedName: what-is-compatibility-testing
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video or read the transcript and answer the questions below.
|
||||
|
||||
# --transcript--
|
||||
|
||||
What is compatibility testing?
|
||||
|
||||
When you build out web applications at scale, you will need to think beyond your personal computing environment. How will these applications work on a variety of devices, operating systems, and browsers? Well, this is where compatibility testing comes in.
|
||||
|
||||
The goal of compatibility testing is to see how well your software works in a variety of different computing environments. This provides the team with the ability to catch bugs before they reach production and will help contribute to a smoother product launch.
|
||||
@@ -46,7 +39,7 @@ To ensure that your applications have no accessibility errors.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -54,7 +47,7 @@ To ensure that your applications are free from linting and formatting errors.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -66,7 +59,7 @@ To ensure that your applications only work for different Linux distributions.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
|
||||
+8
-15
@@ -1,22 +1,15 @@
|
||||
---
|
||||
id: 67d2ff7a461f62a03e3d1861
|
||||
title: What Is Performance Testing?
|
||||
challengeType: 11
|
||||
videoId: i_df917FLPI
|
||||
challengeType: 19
|
||||
dashedName: what-is-performance-testing
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video or read the transcript and answer the questions below.
|
||||
|
||||
# --transcript--
|
||||
|
||||
What is performance testing?
|
||||
|
||||
If a software application is slow to respond or unstable, that will lead to a poor user experience. Performance testing is what you do when you test an application's speed, responsiveness, scalability, and stability under different workloads. The goal is to resolve any type of performance bottleneck before it reaches your users.
|
||||
|
||||
In this video, we will go through a few types of performance testing.
|
||||
In this lecture, we will go through a few types of performance testing.
|
||||
|
||||
The first type is load testing. A load in this context refers to the amount of work or demand put on a system. Load testing determines how a system behaves during normal and peak load times. The goal is to analyze metrics like response times and resource usage and determine if the current software build is ready or not.
|
||||
|
||||
@@ -42,7 +35,7 @@ Testing for an application's linting, formatting, and stability under different
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -50,7 +43,7 @@ Testing for an application's accessibility, scalability and linting under differ
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -58,7 +51,7 @@ Testing for an application's version control, scalability and formatting under d
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -118,7 +111,7 @@ Load testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -130,7 +123,7 @@ Accessibility testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -138,7 +131,7 @@ Stress testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
|
||||
+7
-14
@@ -1,19 +1,12 @@
|
||||
---
|
||||
id: 67d2ff887d2583a079c02e78
|
||||
title: What Is Security Testing?
|
||||
challengeType: 11
|
||||
videoId: qCZ5bw-f-Zo
|
||||
challengeType: 19
|
||||
dashedName: what-is-security-testing
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video or read the transcript and answer the questions below.
|
||||
|
||||
# --transcript--
|
||||
|
||||
What is security testing?
|
||||
|
||||
The web is a powerful place filled with a wealth of information and activities. But it can also be a dangerous place if you are not careful. There are many hackers and cyber criminals out there looking for new ways to breach websites and compromise data.
|
||||
|
||||
You've probably heard of a few high-profile data breaches that affected billion-dollar companies like Meta and Microsoft. When it comes to working on web applications, you will need to do thorough security testing to help identity vulnerabilities and weaknesses.
|
||||
@@ -102,7 +95,7 @@ Denial-of-Service (DoS) attack
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where common security threats were discussed.
|
||||
Refer to the beginning of the lecture where common security threats were discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -110,7 +103,7 @@ Static application injection
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where common security threats were discussed.
|
||||
Refer to the beginning of the lecture where common security threats were discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -118,7 +111,7 @@ Cross-site Scripting (XSS)
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where common security threats were discussed.
|
||||
Refer to the beginning of the lecture where common security threats were discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
@@ -138,7 +131,7 @@ Unit testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where common security threats were discussed.
|
||||
Refer to the end of the lecture where common security threats were discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -146,7 +139,7 @@ Smoke testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where common security threats were discussed.
|
||||
Refer to the end of the lecture where common security threats were discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -154,7 +147,7 @@ Integration testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where common security threats were discussed.
|
||||
Refer to the end of the lecture where common security threats were discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
|
||||
+11
-18
@@ -1,22 +1,15 @@
|
||||
---
|
||||
id: 67db30fedfa0b22a1a2a570c
|
||||
title: What Is the Software Development Life Cycle, and How Does It Relate to Testing?
|
||||
challengeType: 11
|
||||
videoId: vF3lgT8ApGY
|
||||
challengeType: 19
|
||||
dashedName: what-is-the-software-development-life-cycle-and-how-does-it-relate-to-testing
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video or read the transcript and answer the questions below.
|
||||
|
||||
# --transcript--
|
||||
|
||||
What is the software development life cycle, and how does it relate to testing?
|
||||
|
||||
When working on software teams, it is important to have a process for designing and building out new products and services. The Software Development Life Cycle is commonly used by software teams to build and deploy applications.
|
||||
|
||||
In this video, we will break down the different stages of the Software Development Life Cycle (SDLC) and the role that testing plays in it.
|
||||
In this lecture, we will break down the different stages of the Software Development Life Cycle (SDLC) and the role that testing plays in it.
|
||||
|
||||
Here are the standard stages used in the Software Development Life Cycle:
|
||||
|
||||
@@ -62,7 +55,7 @@ Planning Stage
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer back to the beginning of the video where this was discussed.
|
||||
Refer back to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -70,7 +63,7 @@ Testing Stage
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer back to the beginning of the video where this was discussed.
|
||||
Refer back to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -82,7 +75,7 @@ Deployment Stage
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer back to the beginning of the video where this was discussed.
|
||||
Refer back to the beginning of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
@@ -98,7 +91,7 @@ This is where the team will collect requirements and deadlines from stakeholders
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer back to the beginning of the video where this was discussed.
|
||||
Refer back to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -110,7 +103,7 @@ This is where the team will only focus on UI development.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer back to the beginning of the video where this was discussed.
|
||||
Refer back to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -118,7 +111,7 @@ This is where the team will only create Figma and Sketch mockups of the work to
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer back to the beginning of the video where this was discussed.
|
||||
Refer back to the beginning of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
@@ -138,7 +131,7 @@ Slow development
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -146,7 +139,7 @@ Expensive development
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -154,7 +147,7 @@ UI/UX development
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
|
||||
+1
-8
@@ -1,19 +1,12 @@
|
||||
---
|
||||
id: 67db31349f3ace2c5c803c33
|
||||
title: What Are BDD and TDD?
|
||||
challengeType: 11
|
||||
videoId: kDVeB28NwRY
|
||||
challengeType: 19
|
||||
dashedName: what-are-bdd-and-tdd
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video or read the transcript and answer the questions below.
|
||||
|
||||
# --transcript--
|
||||
|
||||
What are BDD and TDD?
|
||||
|
||||
There are two types of testing approaches that you should be aware of in software development. Those approaches are TDD (Test-Driven Development) and BDD (Behavior-Driven Development).
|
||||
|
||||
Let's first take a look at TDD. Test-Driven Development is a methodology that emphasizes writing tests first before building out the features for an application.
|
||||
|
||||
+2
-9
@@ -1,20 +1,13 @@
|
||||
---
|
||||
id: 67db3180830cf02eb662ecaf
|
||||
title: How Do Assertions Work in Unit Testing?
|
||||
challengeType: 11
|
||||
videoId: dksQqFdxjfc
|
||||
challengeType: 19
|
||||
dashedName: how-do-assertions-work-in-unit-testing
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video or read the transcript and answer the questions below.
|
||||
|
||||
# --transcript--
|
||||
|
||||
How do assertions work in unit testing?
|
||||
|
||||
You were first introduced to assertions and unit testing in a previous lecture video. But as a review, unit testing is what you do when you write tests for units of code. Assertions are used to test that the code is behaving as expected.
|
||||
You were first introduced to assertions and unit testing in a previous lecture. But as a review, unit testing is what you do when you write tests for units of code. Assertions are used to test that the code is behaving as expected.
|
||||
|
||||
In this lecture, we are going to take a closer look at assertions in unit tests and explore some best practices.
|
||||
|
||||
|
||||
+7
-14
@@ -1,19 +1,12 @@
|
||||
---
|
||||
id: 67db31c7ed46f430ce6c2da6
|
||||
title: What Are the Differences Between Mocking, Faking, and Stubbing?
|
||||
challengeType: 11
|
||||
videoId: qUrNunLbee4
|
||||
challengeType: 19
|
||||
dashedName: what-are-the-differences-between-mocking-faking-and-stubbing
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video or read the transcript and answer the questions below.
|
||||
|
||||
# --transcript--
|
||||
|
||||
What are the differences between mocking, faking, and stubbing?
|
||||
|
||||
Mocking is the process of replacing real data with false data that simulates the behavior of real components. This allows testers and developers to test for specific components in the application without having to rely on external dependencies.
|
||||
|
||||
A common use case for mocking data would be when dealing with API calls. Imagine you have a fetch call like this in your application:
|
||||
@@ -102,7 +95,7 @@ Mocking HTML changes.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -110,7 +103,7 @@ Mocking CSS changes.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -122,7 +115,7 @@ Mocking JavaScript string methods.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
@@ -174,7 +167,7 @@ Faking API calls for post requests.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -182,7 +175,7 @@ Faking the styles for an application.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -190,7 +183,7 @@ Faking an HTML file.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
|
||||
+7
-14
@@ -1,19 +1,12 @@
|
||||
---
|
||||
id: 67db3238375ff8340ee1ff90
|
||||
title: What Is A/B Testing?
|
||||
challengeType: 11
|
||||
videoId: mH1Fzx1dyw4
|
||||
challengeType: 19
|
||||
dashedName: what-is-ab-testing
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video or read the transcript and answer the questions below.
|
||||
|
||||
# --transcript--
|
||||
|
||||
What is A/B testing?
|
||||
|
||||
Most of you have a select group of websites that you visit every day. This might include sites like X, Discord, or freeCodeCamp. But have you ever wondered why you often see small changes to the design of your most frequently visited pages? Well, this doesn't happen by accident.
|
||||
|
||||
Companies spend a lot of time analyzing analytics and studying user behavior. They do this to identify pain points in the user experience for their site or application. These companies then use that data to come up with solutions to create a smoother user experience.
|
||||
@@ -46,7 +39,7 @@ This test checks that each unit of code is working correctly.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -54,7 +47,7 @@ This test checks for any accessibility errors in your applications and automatic
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -62,7 +55,7 @@ This test sees how compatible your application is with different operating syste
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the beginning of the video where this was discussed.
|
||||
Refer to the beginning of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
@@ -78,7 +71,7 @@ This allows you to make more impulsive decisions as well as continually redesign
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -86,7 +79,7 @@ This allows you to ensure there are no linting or formatting errors in your code
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -98,7 +91,7 @@ This ensures that your applications will run 10x faster in Linux and Mac environ
|
||||
|
||||
### --feedback--
|
||||
|
||||
Refer to the end of the video where this was discussed.
|
||||
Refer to the end of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
|
||||
+10
-17
@@ -1,19 +1,12 @@
|
||||
---
|
||||
id: 67db3248eceee03588a22b8f
|
||||
title: What Is Alpha and Beta Testing?
|
||||
challengeType: 11
|
||||
videoId: ENiGL9jh7ms
|
||||
challengeType: 19
|
||||
dashedName: what-is-alpha-and-beta-testing
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video or read the transcript and answer the questions below.
|
||||
|
||||
# --transcript--
|
||||
|
||||
What is alpha and beta testing?
|
||||
|
||||
Once the initial development and software testing are complete, it is important to have the application tested by testers and real users. This is where alpha and beta testing come in.
|
||||
|
||||
Alpha testing is done by a select group of testers who go through the application to ensure there are no bugs before it is released into the marketplace. This is part of acceptance testing, which ensures that the software application meets the needs of users before its release.
|
||||
@@ -36,7 +29,7 @@ Accessibility testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the beginning of the video where this was discussed.
|
||||
Review the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -44,7 +37,7 @@ Beta testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the beginning of the video where this was discussed.
|
||||
Review the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -56,7 +49,7 @@ A/B testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the beginning of the video where this was discussed.
|
||||
Review the beginning of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
@@ -72,7 +65,7 @@ Yellow and brown box testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the beginning of the video where this was discussed.
|
||||
Review the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -84,7 +77,7 @@ Red and black box testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the beginning of the video where this was discussed.
|
||||
Review the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -92,7 +85,7 @@ White and blue box testing
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the beginning of the video where this was discussed.
|
||||
Review the beginning of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
@@ -108,7 +101,7 @@ User Accessibility Testing.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the end of the video where this was discussed.
|
||||
Review the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -120,7 +113,7 @@ User Development Testing.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the end of the video where this was discussed.
|
||||
Review the end of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -128,7 +121,7 @@ User Interface Testing.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the end of the video where this was discussed.
|
||||
Review the end of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
|
||||
+10
-17
@@ -1,19 +1,12 @@
|
||||
---
|
||||
id: 67db32542c7075361b06024c
|
||||
title: What Is Regression Testing?
|
||||
challengeType: 11
|
||||
videoId: GtCSmVxE264
|
||||
challengeType: 19
|
||||
dashedName: what-is-regression-testing
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video or read the transcript and answer the questions below.
|
||||
|
||||
# --transcript--
|
||||
|
||||
What is regression testing?
|
||||
|
||||
As an application continues to grow, it is not uncommon to have situations where new changes unintentionally break existing functionality. This is known as a regression.
|
||||
|
||||
To help catch these issues before they happen, you can use regression testing. Regression testing is when you re-run functional tests against parts of your application to ensure that everything still works as expected. If you've implemented bug fixes, enhancements, or even have updates to your configuration, then it's a good idea to perform regression testing.
|
||||
@@ -40,7 +33,7 @@ This re-runs tests for issues found in JavaScript files only and fixes them.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the last part of the video where this was discussed.
|
||||
Review the last part of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -48,7 +41,7 @@ This tests for unknown issues that might have resulted in recent additions to th
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the last part of the video where this was discussed.
|
||||
Review the last part of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -56,7 +49,7 @@ This re-runs tests for known HTML-related issues and fixes them.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the last part of the video where this was discussed.
|
||||
Review the last part of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -76,7 +69,7 @@ This is where new changes unintentionally break JavaScript code only.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the beginning of the video where this was discussed.
|
||||
Review the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -84,7 +77,7 @@ This is where changes break existing HTML and CSS code only.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the beginning of the video where this was discussed.
|
||||
Review the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -96,7 +89,7 @@ This is where new changes enhance existing functionality.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the beginning of the video where this was discussed.
|
||||
Review the beginning of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
@@ -116,7 +109,7 @@ Puppeteer
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the beginning of the video where this was discussed.
|
||||
Review the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -124,7 +117,7 @@ Playwright
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the beginning of the video where this was discussed.
|
||||
Review the beginning of the lecture where this was discussed.
|
||||
|
||||
---
|
||||
|
||||
@@ -132,7 +125,7 @@ Selenium
|
||||
|
||||
### --feedback--
|
||||
|
||||
Review the beginning of the video where this was discussed.
|
||||
Review the beginning of the lecture where this was discussed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
|
||||
Reference in New Issue
Block a user