aboutsummaryrefslogtreecommitdiff
path: root/core/testing
Commit message (Collapse)AuthorAgeFilesLines
...
* testing: add json reportingLaytan Laats2024-07-241-1/+45
|
* fix some bugs with -disable-assertLaytan Laats2024-07-161-2/+2
|
* Imply `#no_capture` to all variadic parametersgingerBill2024-07-141-5/+5
|
* Add more uses of `#no_capture`gingerBill2024-07-141-5/+5
|
* Update `core` to `-strict-style`gingerBill2024-06-291-6/+5
|
* Catch `SIGTRAP` in the test runnerFeoramund2024-06-282-0/+11
| | | | Fixes `panic` for Darwin.
* Let `-vet` be used with `-define:ODIN_TEST_NAMES`Feoramund2024-06-281-1/+4
|
* Work around Windows test failureFeoramund2024-06-181-3/+7
| | | | | | | | | | | | | | | | | | | | I am uncertain why this works, but it does. Previously, `rtti_test` was failing due to non-zero data appearing in the `l_buggy` `Buggy_Struct`. The issue was caused by calling `runtime.default_random_generator` with a pointer to the state, somehow. The pointer could be on the stack or in the heap; it did not matter. I found two workarounds. - One is to move the RNG setup behind the call to `free_all`. - The other is to construct the random generator manually. Despite my digging and testing, I could find no reason as to why this works or what the fundamental issue was to begin with. If anyone comes upon this in the future with direct access to a Windows machine, I recommend stepping through the program with a debugger to investigate more deeply into why this happens.
* Setup default `context.random_generator` for testsFeoramund2024-06-151-0/+4
|
* Merge pull request #3765 from Feoramund/add-short-test-logsJeroen van Rijn2024-06-152-7/+18
|\ | | | | Add `ODIN_TEST_SHORT_LOGS` define
| * Add `ODIN_TEST_SHORT_LOGS` defineFeoramund2024-06-152-7/+18
| | | | | | | | | | Strips out the procedure, date, and time information, for when you just need to know the file, line, and message.
* | Make `testing.fail_now` divergentFeoramund2024-06-152-19/+33
| | | | | | | | This is in line with the old way it worked on Windows.
* | Call `cleanups` after test signalFeoramund2024-06-152-3/+20
|/
* add forced shutdown to new test runnerLaytan Laats2024-06-101-1/+8
| | | | | | | | Currently, a Ctrl+c starts a graceful shutdown of the tests and runner. Sometimes tests get stuck and this would never complete. This simply adds an extra step, if Ctrl+c is given for the second time, just `os.exit` right away.
* add error message for unknown test log levelLaytan Laats2024-06-071-0/+3
| | | | | It would previously just be a compilation error about a missing return statement.
* Fix ad hoc `printf` in test runner signal handlerFeoramund2024-06-021-1/+1
|
* Use `Warning` log level for reporting memory leaksFeoramund2024-06-021-2/+4
| | | | Works well with `-define:ODIN_TEST_LOG_LEVEL=warning`.
* Prevent test runner deadlock on NetBSDFeoramund2024-06-021-0/+13
| | | | Add `pthread_testcancel` to `core:sys/unix`
* Be pedantic about not overwriting Odin errorsFeoramund2024-06-021-4/+5
| | | | | | | | | | | | | | | | | | | I was encountering bounds-check error messages being overwritten during a test, if the test failed for another reason and sent a log message. The original intent of having this check inside of the above `if` block was that if a test sent an error message, then it was assumed an overwrite would be safe, but it's completely possible for a test to fail for a legitimate reason, then do an unrelated bounds check somewhere else that would be buried under the animation. This change will make sure that, no matter what, the progress display will not trigger a clear if a signal was raised. There's still no guarantee that bounds-check messages will be printed properly, and it's best to redirect STDERR. The only way that can be fixed is if they get a similar hook to `context.assertion_failure_proc`.
* Tell user about `ODIN_TEST_RANDOM_SEED` optionFeoramund2024-06-021-1/+5
|
* Keep test runner main thread from using 100% of a CPU coreFeoramund2024-06-021-0/+17
|
* Add `-define:ODIN_TEST_LOG_LEVEL` to set lowest log levelFeoramund2024-06-021-2/+17
|
* Log thread count at test run startFeoramund2024-06-021-0/+10
| | | | | Provides a helpful info message about the option to change how many threads are used per run.
* Make it easier to learn about `ODIN_TEST_CLIPBOARD`Feoramund2024-06-021-0/+1
|
* Add note about `SIGSEGV` edge case on UNIX-likesFeoramund2024-06-021-0/+7
|
* Remove Windows test runner in favor of `libc` implementationFeoramund2024-06-023-251/+1
|
* Expand documentation comment for `ODIN_TEST_NAMES`Feoramund2024-06-021-0/+3
|
* Use more concise way of satisfying `-vet`Feoramund2024-06-021-9/+4
|
* Be specific about platforms not implementing test runner signal handlerFeoramund2024-06-021-1/+1
|
* Catch `SIGILL`, `SIGFPE`, `SIGSEGV` in the test runnerFeoramund2024-06-024-11/+223
|
* Rename `signal_handler.odin` to `signal_handler_libc.odin`Feoramund2024-06-021-0/+0
|
* Remove unneeded importFeoramund2024-06-021-1/+0
|
* Support deterministic random seeding of testsFeoramund2024-06-022-0/+24
| | | | | | | | Add a new option `ODIN_TEST_RANDOM_SEED` which is picked from the cycle counter at startup, if it's not specified by the user. This number is sent to every test in the `T` struct and reset every test (just in case).
* Support `ODIN_TEST_PROGRESS_WIDTH=0`Feoramund2024-06-021-7/+20
| | | | | | | This will automatically calculate how wide the progress bars should be based on the package with the greatest number of tests. The progress width is now capped to 100.
* Report test memory usage only if there's an issueFeoramund2024-06-021-11/+27
| | | | | Adds new option `ODIN_TEST_ALWAYS_REPORT_MEMORY`, for when you always want to see the memory usage report.
* Track memory in the test runner by defaultFeoramund2024-06-021-1/+1
|
* Change test runner options to `SCREAMING_SNAKE_CASE`Feoramund2024-06-021-11/+11
| | | | | This commit also changes the name of `test_select` to `ODIN_TEST_NAMES`, to better conform with the already-existing `-test-name:<name>` option.
* Send terminal control code to `STDOUT` insteadFeoramund2024-06-021-1/+1
| | | | | `STDERR` might be redirected, and this code signals to the terminal to show the cursor again. Otherwise, the cursor will be invisible.
* Fix ANSI redraw eating last log lineFeoramund2024-06-022-2/+12
|
* Remove `safe_heap_allocator` from test runnerFeoramund2024-06-021-9/+3
| | | | | I was under the impression that the default `context.allocator` was not thread-safe, but I've been told that this is not the case.
* Use plain sort for `internal_tests`Feoramund2024-06-021-1/+1
|
* Temporarily disable Windows-specific test runnerFeoramund2024-06-021-0/+7
| | | | | | I do not have a Windows machine to test the refactored test runner, and I am unsure if it would even run correctly on Windows without this disabled.
* Remove unneeded codeFeoramund2024-06-021-6/+0
|
* Refactor the test runnerFeoramund2024-06-027-64/+1134
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Changes - Support multi-threaded testing. - Support `set_fail_timeout` on all platforms. - Display an animated progress report. - Setup all tests with a context logger. - Give all tests their own separate custom allocators. - Support tracking test memory usage. - Display a summary of the failed tests at the end. - Let users select only specific tests to run. - Support copying failed tests to the clipboard to run again. - Support catching SIGINT (CTRL-C) to cancel early. - Record context in cleanup procs. - Write all log messages to STDERR for easy redirection. - Possibly more I've forgotten. New Options - `-define:test_threads=N`: Specify thread count. - `-define:test_thread_memory=B`: Specify initial memory block size in bytes to each thread. - `-define:test_track_memory=true`: Track the memory usage of individual tests. - `-define:test_fancy=false`: Disable animated progress report. - `-define:test_select=package.test_name,...`: Run only select tests. - `-define:test_clipboard=true`: Copy names of failed tests to the clipboard. - `-define:test_progress_width=24`: Change the width of the animated progress bars.
* Merge pull request #3138 from FourteenBrush/mastergingerBill2024-01-291-2/+9
|\ | | | | Add a testing.expectf proc as a way to avoid a tprintf call.
| * Fix typoFourteenBrush2024-01-251-1/+1
| |
| * Need to unpack argsFourteenBrush2024-01-251-1/+1
| |
| * Forgot to include loc paramFourteenBrush2024-01-251-2/+1
| |
| * Merge branch 'master' of https://github.com/FourteenBrush/OdinFourteenBrush2024-01-251-2/+2
| |\
| * | Add testing.expectfFourteenBrush2024-01-251-0/+8
| | |
generated by cgit v1.2.3 (git 2.39.1) at 2026-02-15 09:47:01 +0000