单元测试业力跑步者/茉莉花分析

unit-tests karma-runner/jasmine profiling(单元测试业力跑步者/茉莉花分析)

问题描述

对于单元测试，我们使用 grunt/karma-runner/jasmine/phantom.js.因为我们试图涵盖任何新功能，所以许多单元测试迅速增长.而且，不幸的是，测试时间也在增加.现在它并不重要，1000 次测试需要 10 秒，但它会越来越差.

For unit-tests we use grunt/karma-runner/jasmine/phantom.js. Because we try to cover any new functionality, a number of unit-tests grows up rapidly. And, unfortunately, time for tests also increasing. Now it is not critical and takes 10 seconds for 1000 tests, but it goes worse and worse.

还有问题:

1. 我知道，有些测试写得不好(很费时间)，但我应该优化哪一个?是否存在一些 karma/jasmine profiler 来测量每个测试的执行时间?

1. I know, some of the tests are bad-written (a lot of time consuming), but which one I should optimize? Is it exist some karma/jasmine profiler which measure time execution for each test?

我可以启动更多的 karma-runner 线程/进程，因为 CPU 只使用了 5%-10%?单元测试真正独立.

Can I start more karma-runner threads/processes, because CPU used only for 5%-10%? Unit-tests really independent.

每次我保存文件时，karma:watch 都会启动所有测试，可能存在 karma-runner 的某些选项，它仅重新启动当前文件夹的测试(我们使用规则: 单元测试 file.spec.js 存储在与源 file.js 相同的文件夹中)?

Each time when I save file, karma:watch starts all tests, may be exist some option for karma-runner, which re-starts only tests for current folder (we use rule: unit tests file.spec.js stored in the same folder as source file.js)?

谢谢，

update1:​​有人建议我使用 iit/ddescribe for jasmine(与 .only 用于 mocha 相同)和这是开发/调试的绝佳选择，但可能以其他方式存在?

update1: Someone suggest me use iit/ddescribe for jasmine (the same as .only for mocha) and it is great option for develop/debugging, but may be exist some other way ?

我将问题发布到业力用户论坛此处.

I post the question to karma-user forum here.

推荐答案

寻找慢速测试

• reportSlowerThan(点或进度报告器将以毫秒为单位报告所有比给定数字慢的测试)，

• reportSlowerThan (dots or progress reporter will report all the tests that are slower than given number in ms),

您可以跳到浏览器并以与应用程序相同的方式分析您的测试(例如.flamecharts 在 Chrome 中很棒).

you can jump to the browser and profile your tests in the same way you would do it with an app (eg. flamecharts in Chrome are awesome).

加快测试速度

• 并行化:

我们正在努力解决这个问题.您将能够跨多个浏览器并行化测试.当然，这些浏览器不必在同一台机器上运行，因此您也可以使用多台机器.

We are working on this. You will be able to parallelize the tests across multiple browsers. Of course, these browsers don't have to run on the same machine so you will be able to use multiple machines too.

我认为运行多个 Karma 实例本身并没有太大帮助，因为它是以非常非阻塞"的方式编写的，而且我还没有看到它是瓶颈.然而，我们应该优化 CPU/内存使用.v0.12 将在这方面进行大量改进.

I don't think running multiple instances of Karma itself would help that much, as it is written in a very "non-blocking" way and I haven't seen it to be the bottleneck. We should however optimize the CPU/memory usage. A lot of improvements in this area is coming in v0.12.

只运行一部分测试:

你应该完全使用 iit/ddescribe (Jasmine).为什么这对你不起作用?顺便提一句.Mocha 的 it.only() 和 describe.only() 的实现有问题，所以我推荐 Jasmine(或修复 Mocha).

You should totally use iit/ddescribe (Jasmine). Any reason why this does not work for you? Btw. Mocha's implementation of it.only() and describe.only() has issues, so I recommend Jasmine (or fixing Mocha).

还有一个 Google Closure plugin 的原型，它只加载你真正需要的文件需要(假设您 iit 进行一次测试，它只会加载/解析/评估您真正需要的 iit 文件).这显着缩短了大型项目的启动时间——我们应该为其他模块加载器(RequireJS、CommonJS)做类似的技巧.

There is also a prototype of Google Closure plugin which only loads the files you really need (say you iit one test, it will only load/parse/evaluate the files you really need for that iit). This improves start time on huge projects significantly - we should do similar tricks for other module loaders (RequireJS, CommonJS).

编写更快的代码:

你可能已经知道了... ;-)

You probably know this already... ;-)

DOM 很慢.逻辑/DOM 的良好分离将允许您在不实际接触 DOM 的情况下测试更多内容.如果您使用 Angular，您可以查看 测试指令示例.

DOM is slow. A good separation of logic/DOM will allow you to test more stuff without actually touching DOM. If you use Angular, you might check out the testing directives example.

使用依赖注入模式有很大帮助，因为您基本上可以最大限度地减少为每个测试准备(以及拆除)所需的环境.这是一个例子.

Using Dependency Injection pattern helps a lot as you basically minimize the environment you need to prepare (and also tear down) for each test. Here's an example.

一般来说，较低的测试速度更快.我认为最好用尽可能少的测试来涵盖每个功能/问题.

In general, lower lower tests are faster. I think it's good to cover each functionality/issue with lowest possible test.

消除内存泄漏:

如果您的测试泄漏内存，浏览器会变得越来越慢，因此测试编号 1000 会非常慢，即使它写得很好.确保每个测试都释放所有引用.您可以使用 http://localhost:9876/debug.html 并分析内存.在执行之前检查内存(在 Jasmine 执行所有 describe() 块并收集测试之后)然后在执行测试之后 - 它应该是相同的.

If your tests leak memory, the browser will get slower and slower and so the test number 1000 will be pretty slow even though it's well written. Make sure each test frees up all the references. You can use http://localhost:9876/debug.html and profile the memory. Check the memory before executing (after Jasmine executed all the describe() blocks and collected the tests) and then after executing the tests - it should be the same.

发现一些内存泄漏比其他的更难，但它可以显着提高速度 - 我已经看到仅通过消除内存泄漏从大约 5 分钟到不到 1 分钟.

Finding some memory leaks is harder than others, but it can significantly improve the speed - I've seen stuff like from ~5mins to under a minute just by eliminating memory leaks.

这篇关于单元测试业力跑步者/茉莉花分析的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持编程学习网！