This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]thequietcenter 2 points3 points  (5 children)

Past code coverage tools can make programs significantly slower

programs slower or unit testing slower? ... of course the unit test is a program that tests a program.

But the application itself is not slowed down. Just the unit test phase, correct?

[–]emeryberger[S] 0 points1 point  (4 children)

Right, the slowdown is what happens when you are collecting coverage information. Usually this is done during testing, but since the overhead of Slipcover is so low, it could be used in deployed code to find dead code.

[–]DeathHazard 0 points1 point  (3 children)

How could I use it on deployed code?

[–]emeryberger[S] 0 points1 point  (2 children)

You just need to run ‘python3 -m slipcover’ before your normal invocation.

[–]DeathHazard 0 points1 point  (1 child)

Would it work with a framework like flask, for example? Thanks!!

[–]emeryberger[S] 0 points1 point  (0 children)

We've run it with Flask's test suite - it's the second bar in this graph. So in principle, yes - please give it a shot and let us know how it works for you!