The test does not provide significant test coverage, so if itMy question may boil down to what is "significant," I think.
passes, that does not necessarily mean that the package under test
is actually functional.
If a superficial test fails, it will be treated like any other
failing test, but if it succeeds, this is only a weak indication of
success. Continuous integration systems should treat a package where
all non-superficial tests are skipped as equivalent to a package
where all tests are skipped.
For example, a C library might have a superficial test that simply
compiles, links and executes a "hello world" program against the
library under test but does not attempt to make use of the library's functionality, while a Python or Perl library might have a
superficial test that runs import foo or require Foo; but
does not attempt to use the library beyond that.
Note that in their reference to building a 'Hello, world' program, the specification says that what makes the test superficial is that the
library's functionality isn't used in the 'Hello, world' program, but
merely linking against it is tested. Since I'm testing GCC, Newlib
(which provides the I/O functions), and the simulator in combination,
is building and running such relatively simple programs appropriate to
say that the tests provide good coverage?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 90:37:42 |
Calls: | 6,658 |
Files: | 12,203 |
Messages: | 5,334,093 |