Software Testing Explained in 100 Seconds

[00:00] software it's not like engineering

[00:02] something easy like a bridge where you

[00:03] start with a blueprint

[00:04] build it to spec then forget about it

[00:06] software is dynamic with a lot of moving

[00:08] parts and requirements that evolve over

[00:10] time

[00:11] developers build apps on top of a

[00:12] mountain of abstractions and nobody

[00:14] fully understands how every layer works

[00:16] that's okay because we just need to make

[00:18] sure that our code matches the

[00:19] requirements of the product test driven

[00:21] development is scientifically proven to

[00:23] reduce defects and improve the

[00:25] maintainability of a code base but it

[00:26] does require some additional effort

[00:28] one option is manual testing where a

[00:30] human being clicks on every button and

[00:32] fills out every form then assigns a

[00:34] bunch of jira tickets so they can be

[00:35] backlogged by the developers

[00:37] but that's not very efficient for a

[00:38] large scale product a better approach is

[00:41] to use automated testing tools that

[00:42] allow developers to write code for the

[00:44] sole purpose of testing the main

[00:46] application code in a code base you'll

[00:48] often find files that end in

[00:49] test or dot spec inside you'll first

[00:52] find a line of code that describes the

[00:54] feature or thing that's being tested

[00:56] that's known as a test suite and it

[00:57] contains one or more individual tests

[01:00] an individual test usually starts with

[01:02] it followed by a description

[01:03] of what is being tested the idea is to

[01:06] describe the behavior of the code in

[01:07] human readable terms

[01:09] inside the test the code will be

[01:10] executed then one or more

[01:12] expectations or assertions are used to

[01:14] check that the code produces the

[01:16] expected result if the expectation

[01:18] returns false then the test fails

[01:20] if it's true it passes test runners like

[01:22] jest or karma

[01:23] can run all your tests automatically in

[01:25] the background or on a continuous

[01:26] integration server before you deploy

[01:28] now there are many different automated

[01:30] testing strategies that you should be

[01:32] aware of

[01:32] at the most granular level we have unit

[01:34] testing which is designed to test

[01:36] individual functions or methods

[01:37] like does this function return the

[01:39] proper value when given the arguments of

[01:41] a

[01:41] and b then we have integration testing

[01:43] to determine how well different

[01:44] components or modules work together like

[01:46] is the component

[01:47] able to use the database service to get

[01:49] data from the server at the highest

[01:51] level we have end-to-end testing which

[01:53] usually happens in a mock browser or

[01:54] device

[01:55] and simulates actual user behaviors like

[01:57] clicking on buttons and filling out

[01:59] forms

[01:59] it's like having a robot to do all your

[02:01] manual testing for you

[02:02] and that's not all there are many other

[02:04] types like performance and smoke testing

[02:06] which i'll explain

[02:07] in my upcoming test driven development

[02:09] breakdown hit the like button if you

[02:10] want to see more short videos like this

[02:12] thanks for watching and i will see you

[02:14] in the next one