How to use Angular CLI for unit testing and E2E testing

This article mainly introduces the method of using Angular CLI for unit testing and E2E testing. Now I share it with you and give it as a reference.

Unit testing.

angular cli uses karma for unit testing.

First execute ng test --help or ng test -h View help.

To execute the test, just execute ng test. It will execute all .spec.ts files in the project.

And it will also detect changes in the files. If the file changes, then it will re-execute the test.

It should be executed in a separate terminal process.

First create an angular project, with routing:

ng new sales --routing

After creating the project, directly execute the command test:

ng test

Then a page will pop up, which is the test result data.

I will add a few more below components and an admin module:

ng g c person
ng g c order
ng g m admin --routing
ng g c admin/user
ng g c admin/email

Then configure the routing, and the most important thing is to get this effect:

At this time, I re-execute ng test:

Although the program runs without problems, there is still a problem in the test: router-outlet is not an angular component.

You can take a look at the spec list:

At this time, because the admin module runs independently when running the test, the module does not reference the Router module, so the router cannot be recognized. -outlet.

So how to solve this problem?

Open admin.component.spec.ts:

Fill in this sentence on, then there will be no errors:

NO_ERRORS_SCHEMA tells angular to ignore those unrecognized elements or element attributes.

1. -- code-coverage -cc code coverage report, this is not enabled by default because the speed of generating reports is still relatively slow.

2. --colors output results using various colors is enabled by default

3. --single-run -sr executes the test, but does not detect file changes and is not enabled by default

4. --progress outputs the test process Go to the console and enable by default

5. --sourcemaps -sm Generate sourcemaps Enable by default

6. --watch -w Run the test once and detect changes Turned on by default

ng test is to run the test, and if the file changes, the test will be re-run.

Use ng test -sr or ng test -w false to execute Single test

Test code coverage:

ng test --cc report is generated in the /coverage folder by default, but it can be modified by modifying the properties in .angular-cli.json Make modifications.

The code coverage report is generated below:

ng test -sr -cc

Usually used with the -sr parameter (run a test).

Then it will be in the project coverage file Some files are generated in the folder:

Open index.html directly:

You can see that they are all 100%, This is because I didn't write any code.

Then I added some code in the user component:

Run ng test again --sr -cc :

##You can see that this part of the code is not covered.

If I change the code to canGetUsers is true:

Execute ng test --sr -cc

again and you can see that the code coverage has changed this time:

Only the catch part is not covered.

I think the built-in function of code coverage is very good.

Debug单元测试.

首先执行ng test:

然后点击debug, 并打开开发者工具:

然后按cmd+p:

找到需要调试的文件:

设置断点:

然后在spec里面也设置一个断点:

最后点击浏览器的刷新按钮即可:

E2E测试的参数.

实际上angular cli是配合着protractor来进行这个测试的.

它的命令是 ng e2e.

常用的参数有:

1. --config -c 指定配置文件 默认是 protractor.conf.js

2. --element-explorer -ee 打开protractor的元素浏览器

3. --serve -s 在随机的端口编译和serve 默认true

4. --specs -sp 默认是执行所有的spec文件, 如果想执行某个spec就使用这个参数, 默认是all

5. --webdriver-update -wu 尝试更新webdriver 默认true

通常执行下面机组命令参数组合即可:

ng e2e
ng e2e -ee

Debug E2E测试.

看一下项目:

配置文件protractor.conf.js已经配置好.

而测试文件是在e2e目录下.

看一下spec和po文件:

再看一下app.component.html里面的值:

应该是没问题的.

所以执行ng e2e:

测试通过, 但是浏览器闪了一下就关闭了.

如果我想debug e2e, 那么执行这个命令:

ng e2e -ee

由于我使用的是mac, 当前这个命令在mac上貌似确实有一个bug:

如果可以正常运行这个命令的话, 终端窗口会出现“Debugger listening on xxx: ”字样, 然后就可以在下面输入变量或者表达式来查看它们的值从而进行调试了.

如果想退出调试, 那就按Ctrl+c或者输入.exit即可.

上面是我整理给大家的，希望今后会对大家有帮助。

相关文章：

Vue.js 表单控件操作小结

js传递数组参数到后台controller的方法

Vue.js实现可配置的登录表单代码详解

The above is the detailed content of How to use Angular CLI for unit testing and E2E testing. For more information, please follow other related articles on the PHP Chinese website!