Files
Ashin Walpola d107534eb2 Keep vanetza-idf in obu-firmware, so a plain clone builds the firmware
obu-firmware builds against the vanetza-idf C-ITS library, which until now
came from the colleague's microbu-esp32c5 tree beside the repository and was
not tracked here, so a clone of this repository could not build the firmware
it ships. The library alone is now part of obu-firmware, as
obu-firmware/external/vanetza-idf: their external/vanetza-idf at commit
cf4b99f, unchanged (9775 files; see its PROVENANCE.md). CMake takes it from
there by default; -DVANETZA_IDF_DIR still points the build elsewhere.

The rest of the colleague's tree (their own VAM firmware, PKI tooling,
station-link Python tools, the V2X2MAP bridge) stays out of this repository
and gitignored; nothing is pushed to their repository. NOTES.md, docs/06,
TODO.md and the pcap verifier's usage line point at the new location.
2026-09-24 10:56:05 +02:00

24 lines
532 B
C++

#include <gtest/gtest.h>
#include <vanetza/dcc/channel_load.hpp>
using namespace vanetza::dcc;
TEST(ChannelLoad, ctor)
{
ChannelLoad cl1;
EXPECT_DOUBLE_EQ(0.0, cl1.value());
ChannelLoad cl2(30, 250);
EXPECT_DOUBLE_EQ(0.12, cl2.value());
ChannelLoad cl3(0, 0);
EXPECT_DOUBLE_EQ(0.0, cl3.value());
}
TEST(ChannelLoadRational, less)
{
EXPECT_LT(ChannelLoad(30, 100), ChannelLoad(31, 100));
EXPECT_LT(ChannelLoad(30, 100), ChannelLoad(8, 25));
EXPECT_LT(ChannelLoad(0,10), ChannelLoad(1, 2));
}