ut
test
Our great sponsors
ut | test | |
---|---|---|
10 | 3 | |
1,183 | 232 | |
1.4% | -0.9% | |
7.0 | 5.4 | |
13 days ago | about 1 month ago | |
C++ | Elm | |
Boost Software License 1.0 | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ut
-
[C++20][safety] static_assert is all you need (no leaks, no UB)
I don't think stepping through static_assert is a thing? Curious if it is, though. Since constexpr is either run-time or compile-time and static_assert is not a poor man's debugging facility could be to -Dstatic_assert(...) assert(__VA_ARGS__) and gdb the code. Alternatively, a more refined solution would be to use an UT framework (for example https://github.com/boost-ext/ut) which helps with that. IMHO, TDD can also limit the requirement of stepping into the code and with gurantees that the code is memory safe and UB safe there is less need for sanitizers and valgrind etc. depending on the coverage.
-
snatch -- A lightweight C++20 testing framework
Have you compared with Boost UT, or was this targeted at keeping things catch2-like?
It was not easy, I had to modify Boost UT to get it to run my tests. It doesn't support type-parametrized tests when the type parameter is non-copiable, which was the case for me. This is a symptom of a larger issue, which is that it relies on std::apply and std::tuple to generate the type-parametrized tests, which in turns requires instantiating the tuple and the contained objects (even though these instances aren't actually used; eh). That's a no go for me, since I need to carefully monitor when instance are created, and this was throwing off my test code. I had to effectively disable these checks to get it to run without failures. Then there was a similar issue with expect(), which doesn't work if part of the expression is non-copiable. I reported these issues to them.
-
[C++20] New way of meta-programming?
https://github.com/boost-ext/ut (for better user interface when defining tests without macros)
-
Getting started with Boost in 2022
https://github.com/boost-ext/ut from Kris Jusiak is worth checking
- How to unit test
-
Calculate Your Code Performance
C++: C++ has quite a number of benchmarking libraries some of the recent ones involving C++ 20's flexibility. The most notable being Google Bench and UT. C does not have many specific benchmarking libraries, but you can easily integrate C code with C++ benchmarking libraries in order to test the performance of your C code.
-
Benchmarking Code
UT
-
Another C++ unit testing framework without macros
By Boost.UI you mean this?
In Boost.UT there is a number of different styles to add a parametrized test case. All of them are pretty cryptic bue to heavy isage of oeverloaded operators of custom "non-public" classes. Except for the for-loop method, in all other methods the list of parameter values goes after the test procedure definition. I find this inconvenient, as I want to see list of parameter value next to the test name. This is what I used to from the times I was coding a lot of unit tests in C#.
test
-
Setting up an Elm project in 2022
The de-facto standard for testing an Elm application is elm-test. However, as noted in the README:
-
Porting Elm to WebAssembly
Once all that handwritten C code was solid, I needed to make sure the C generated from Elm was working properly. I found the source for the core library's unit tests and decided to port them into my project and add some of my own tests. You can run the tests in WebAssembly in your browser too. (Funnily enough, one of the biggest challenges was getting the Elm Test framework itself to run! The framework is more complex than the tests themselves. I still need to come back to the fuzzer tests!)
-
Causing Bedlam in Elm
Lesson Learned: Elm has built in recursion improvements for a variety of positive reasons, and you should think in recursion to solve looping problems. Use property/fuzz tests and bounds checking with early exit to prevent this from locking up your UI (i.e if > 9000, omg abort). If you’re algorithm is reasonable, but the data set is just gigantic, offload to a server instead for more horsepower. Or Workers if you don’t have server chops, can’t upload the large data, or don’t trust your server devs. (“But Doc, I’m the server dev!” Good joke. Ever̸y̴b̸ody laugh. Roll on s̵͓̆nâ̶̱re drum. Curtains.)
What are some alternatives?
Boost.Test - The reference C++ unit testing framework (TDD, xUnit, C++03/11/14/17)
Catch - A modern, C++-native, test framework for unit-tests, TDD and BDD - using C++14, C++17 and later (C++11 support is in v2.x branch, and C++03 on the Catch1.x branch)
FakeIt - C++ mocking made easy. A simple yet very expressive, headers only library for c++ mocking.
Google Test - GoogleTest - Google Testing and Mocking Framework
test - A library for writing unit tests in Dart.
KmTest - Kernel-mode C++ unit testing framework in BDD-style
doctest - The fastest feature-rich C++11/14/17/20/23 single-header testing framework
GUnit - GUnit - Google.Test/Google.Mock/Cucumber on steroids
orbit - C/C++ Performance Profiler
CppUTest - CppUTest unit testing and mocking framework for C/C++
benchmark - A microbenchmark support library
nanobench - Simple, fast, accurate single-header microbenchmarking functionality for C++11/14/17/20