Update README and add contrib dir
This commit is contained in:
19
contrib/traffic-generator/test/examples-to-run.py
Normal file
19
contrib/traffic-generator/test/examples-to-run.py
Normal file
@@ -0,0 +1,19 @@
|
||||
#! /usr/bin/env python3
|
||||
|
||||
# A list of C++ examples to run in order to ensure that they remain
|
||||
# buildable and runnable over time. Each tuple in the list contains
|
||||
#
|
||||
# (example_name, do_run, do_valgrind_run).
|
||||
#
|
||||
# See test.py for more information.
|
||||
cpp_examples = [
|
||||
("traffic-generator-ethernet", "True", "True"),
|
||||
]
|
||||
|
||||
# A list of Python examples to run in order to ensure that they remain
|
||||
# runnable over time. Each tuple in the list contains
|
||||
#
|
||||
# (example_name, do_run).
|
||||
#
|
||||
# See test.py for more information.
|
||||
python_examples = []
|
||||
@@ -0,0 +1,86 @@
|
||||
|
||||
// Include a header file from your module to test.
|
||||
#include "ns3/traffic-generator.h"
|
||||
|
||||
// An essential include is test.h
|
||||
#include "ns3/test.h"
|
||||
|
||||
// Do not put your test classes in namespace ns3. You may find it useful
|
||||
// to use the using directive to access the ns3 namespace directly
|
||||
using namespace ns3;
|
||||
|
||||
// Add a doxygen group for tests.
|
||||
// If you have more than one test, this should be in only one of them.
|
||||
/**
|
||||
* \defgroup traffic-generator-tests Tests for traffic-generator
|
||||
* \ingroup traffic-generator
|
||||
* \ingroup tests
|
||||
*/
|
||||
|
||||
// This is an example TestCase.
|
||||
/**
|
||||
* \ingroup traffic-generator-tests
|
||||
* Test case for feature 1
|
||||
*/
|
||||
class TrafficGeneratorTestCase1 : public TestCase
|
||||
{
|
||||
public:
|
||||
TrafficGeneratorTestCase1();
|
||||
virtual ~TrafficGeneratorTestCase1();
|
||||
|
||||
private:
|
||||
void DoRun() override;
|
||||
};
|
||||
|
||||
// Add some help text to this case to describe what it is intended to test
|
||||
TrafficGeneratorTestCase1::TrafficGeneratorTestCase1()
|
||||
: TestCase("TrafficGenerator test case (does nothing)")
|
||||
{
|
||||
}
|
||||
|
||||
// This destructor does nothing but we include it as a reminder that
|
||||
// the test case should clean up after itself
|
||||
TrafficGeneratorTestCase1::~TrafficGeneratorTestCase1()
|
||||
{
|
||||
}
|
||||
|
||||
//
|
||||
// This method is the pure virtual method from class TestCase that every
|
||||
// TestCase must implement
|
||||
//
|
||||
void
|
||||
TrafficGeneratorTestCase1::DoRun()
|
||||
{
|
||||
// A wide variety of test macros are available in src/core/test.h
|
||||
NS_TEST_ASSERT_MSG_EQ(true, true, "true doesn't equal true for some reason");
|
||||
// Use this one for floating point comparisons
|
||||
NS_TEST_ASSERT_MSG_EQ_TOL(0.01, 0.01, 0.001, "Numbers are not equal within tolerance");
|
||||
}
|
||||
|
||||
// The TestSuite class names the TestSuite, identifies what type of TestSuite,
|
||||
// and enables the TestCases to be run. Typically, only the constructor for
|
||||
// this class must be defined
|
||||
|
||||
/**
|
||||
* \ingroup traffic-generator-tests
|
||||
* TestSuite for module traffic-generator
|
||||
*/
|
||||
class TrafficGeneratorTestSuite : public TestSuite
|
||||
{
|
||||
public:
|
||||
TrafficGeneratorTestSuite();
|
||||
};
|
||||
|
||||
TrafficGeneratorTestSuite::TrafficGeneratorTestSuite()
|
||||
: TestSuite("traffic-generator", UNIT)
|
||||
{
|
||||
// TestDuration for TestCase can be QUICK, EXTENSIVE or TAKES_FOREVER
|
||||
AddTestCase(new TrafficGeneratorTestCase1, TestCase::QUICK);
|
||||
}
|
||||
|
||||
// Do not forget to allocate an instance of this TestSuite
|
||||
/**
|
||||
* \ingroup traffic-generator-tests
|
||||
* Static variable for test initialization
|
||||
*/
|
||||
static TrafficGeneratorTestSuite strafficGeneratorTestSuite;
|
||||
Reference in New Issue
Block a user