Fix api_test documentation. (#3013)

* fix documentation.

* Update docs/GettingStarted.md

Co-authored-by: Dave Thaler <dthaler1968@gmail.com>

---------

Co-authored-by: Dave Thaler <dthaler1968@gmail.com>

docs/GettingStarted.md

@@ -303,8 +303,11 @@ by having the mocked extensions emit events.
 This test exercises various eBPF user mode eBPF APIs, including those to load programs,
 enumerate maps and programs etc. This test requires the eBPF user mode service (EbpfSvc), and the
 kernel execution context (`EbpfCore.sys`) and the Network Extension (`NetEbpfExt.sys`) to be running.
-This test is currently *not* part of the CI pipeline. Developers must run this test manually before
-checking in changes.
+There is a group of tests in this suite with tag "*regression-tests*". These tests are used to ensure
+any release of the eBPF framework is backwards compatible, so that a program from
+a previous release can run against the latest release. If this test suite is run manually, then the corresponding
+test from the previous release would need to be copied locally on the test machine. Alternatively `~[regression_tests]`
+can be specified in the command-line to skip these tests.
 
 ### sample_ext_app.exe
 

tests/api_test/api_test.cpp

@@ -1047,7 +1047,7 @@ test_sock_addr_native_program_load_attach(const char* file_name)
 }
 
 #define DECLARE_REGRESSION_TEST_CASE(version)                                                         \
-    TEST_CASE("test_native_program_load_attach-regression-" #version)                                 \
+    TEST_CASE("test_native_program_load_attach-regression-" #version, "[regression_tests]")           \
     {                                                                                                 \
         test_sock_addr_native_program_load_attach((const char*)"cgroup_sock_addr2_"##version ".sys"); \
     }