|
From: <no...@tc...> - 2025-10-17 12:18:56
|
Automated mail by fx, on behalf of no...@tc... Ticket Change [a5d61ff70720584e9df5544c3d2024a6a922a2754378c62cc42d17593582524e] [Skip test files entirely if all tests are skipped] By erikleunissen For Tk On 2025-10-17T12:15:14.476 Details https://core.tcl-lang.org/tk/tinfo?name=a5d61ff70720584e9df5544c3d2024a6a922a2754378c62cc42d17593582524e Ticket https://core.tcl-lang.org/tk/tktview/83eed90f933b64378b689b8b87c9777b903c280e Changed Fields comment: SKIP TEST FILES ENTIRELY IF ALL TESTS ARE SKIPPED ================================================= Some test files have all of their tests skipped under circumstances where a certain test constraint isn't satisfied. Test constraints that have such a wholesale effect are mostly related to the platform, the operating system, or the windowing system. But a few other test constraints also induce this "skipping of all tests". The table below lists these "wholesale" constraints along with the pertaining test files. Constraints Testfiles ---------------------------------------------------------------------- -------- x11 unixFont.test, unixSelect.test unix unixButton.test, unixEmbed.test, unixMenu.test, unixWm.test win winButton.test, winClipboard.test, window.test, winFont.test, winfo.test, winMenu.test, winMsgbox.test, winSend.test, winWm.test nt or testwinevent winDialog.test testutils testutils.test ---------------------------------------------------------------------- -------- This RFE proposes to skip evaluation of the entire test file in these cases (using the command tcltest::skipFiles). Advantages ---------- To appreciate the advantages, it's essential to understand what it encompasses to evaluate a test file, even if all of its tests are skipped. The "skipping of all tests in a test file" does not mean: "skipping execution of the test commands in the test file". On the contrary: all test commands in a testfile are always executed, even if circumstances don't meet the test's constraints. It's just that test commands for skipped tests do not lead to any further proper testing exercise where the -setup, -body and -result clauses are being evaluated. Even if no tests are actually run, the evaluation of test files also means that: a. testfile initialization, support code like local utility procs, and common setup sections for certain groups of tests is executed (to no avail). b. some code blocks need conditions involving one of the same test constraints that are listed above, ...((truncated)) login: erikleunissen ------------------------------------------------------------ See Tcl/Tk development @ http://core.tcl-lang.org/ ------------------------------------------------------------ |