#unittest — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #unittest, aggregated by home.social.
-
I know I'm a geek - but there's a certain degree of satisfaction in having a test made to fail after a refactoring actually fail as expected and then implementing the fix as expected.
And to imagine some people want to offload that satisfaction to a LLM tsk tsk tsk.
-
I know I'm a geek - but there's a certain degree of satisfaction in having a test made to fail after a refactoring actually fail as expected and then implementing the fix as expected.
And to imagine some people want to offload that satisfaction to a LLM tsk tsk tsk.
-
We just shipped Core Framework v3 4.0.0-pre.108 and Analyzers 2.0.0-pre.51.
This release adds new features, new analyzers, and fixed several bugs. We anticipate these being the final prerelease builds of this cycle. Please test thoroughly!
https://xunit.net/releases/v3/4.0.0-pre.108
https://xunit.net/releases/analyzers/2.0.0-pre.51 -
We just shipped Core Framework v3 4.0.0-pre.108 and Analyzers 2.0.0-pre.51.
This release adds new features, new analyzers, and fixed several bugs. We anticipate these being the final prerelease builds of this cycle. Please test thoroughly!
https://xunit.net/releases/v3/4.0.0-pre.108
https://xunit.net/releases/analyzers/2.0.0-pre.51 -
We just shipped Core Framework v3 4.0.0-pre.108 and Analyzers 2.0.0-pre.51.
This release adds new features, new analyzers, and fixed several bugs. We anticipate these being the final prerelease builds of this cycle. Please test thoroughly!
https://xunit.net/releases/v3/4.0.0-pre.108
https://xunit.net/releases/analyzers/2.0.0-pre.51 -
We just shipped Core Framework v3 4.0.0-pre.108 and Analyzers 2.0.0-pre.51.
This release adds new features, new analyzers, and fixed several bugs. We anticipate these being the final prerelease builds of this cycle. Please test thoroughly!
https://xunit.net/releases/v3/4.0.0-pre.108
https://xunit.net/releases/analyzers/2.0.0-pre.51 -
We just shipped Core Framework v3 4.0.0-pre.108 and Analyzers 2.0.0-pre.51.
This release adds new features, new analyzers, and fixed several bugs. We anticipate these being the final prerelease builds of this cycle. Please test thoroughly!
https://xunit.net/releases/v3/4.0.0-pre.108
https://xunit.net/releases/analyzers/2.0.0-pre.51 -
There will be another prerelease coming this weekend.
Since we like to have prerelease builds stable for a month before declaring them release, please make sure to use the current and upcoming builds to verify, especially with Native AOT.
Thanks!
-
🔥 A decade-old unit test with an existential crisis set for 2026—because nothing screams foresight like a ticking time bomb in your codebase. 🧨 Meanwhile, Mastodon reminds us that enabling #JavaScript is still a revolutionary act in the web 3.0 era. 💻
https://mastodon.social/@jdm_/116429380667467307 #unitTest #existentialCrisis #web3 #revolution #codingMastodon #HackerNews #ngated -
Based on this poll, we will be removing support for Visual Studio 2019 and out-of-support versions of Visual Studio 2022 from `xunit.analyzers` sometime before the final 2.0.0 release.
-
Based on this poll, we will be removing support for Visual Studio 2019 and out-of-support versions of Visual Studio 2022 from `xunit.analyzers` sometime before the final 2.0.0 release.
-
Based on this poll, we will be removing support for Visual Studio 2019 and out-of-support versions of Visual Studio 2022 from `xunit.analyzers` sometime before the final 2.0.0 release.
-
Based on this poll, we will be removing support for Visual Studio 2019 and out-of-support versions of Visual Studio 2022 from `xunit.analyzers` sometime before the final 2.0.0 release.
-
Based on this poll, we will be removing support for Visual Studio 2019 and out-of-support versions of Visual Studio 2022 from `xunit.analyzers` sometime before the final 2.0.0 release.
-
We just shipped Core Framework v3 4.0.0-pre.81, Analyzers 2.0.0-pre.40, and VS Adapter 4.0.0-pre.4.
This release adds several new analyzers and fixes many bugs, especially related to Native AOT support.
https://xunit.net/releases/v3/4.0.0-pre.81
https://xunit.net/releases/analyzers/2.0.0-pre.40
https://xunit.net/releases/visualstudio/4.0.0-pre.4 -
Do you write custom TraitAttribute-derived attributes? Do you think they'd be useful in the core framework? If so, chime in with your suggestions here: https://github.com/xunit/xunit/discussions/3537
-
We just shipped Core Framework v3 4.0.0-pre.33, Analyzers 2.0.0-pre.9, and VS Adapter 4.0.0-pre.3.
This prerelease build adds support for Native AOT, in addition to bug fixes.
https://xunit.net/releases/v3/4.0.0-pre.33
https://xunit.net/releases/analyzers/2.0.0-pre.9
https://xunit.net/releases/visualstudio/4.0.0-pre.3 -
I have an older legacy project where integration tests isn't set up and would be quite complex to do, so using "unit tests" mechanics via substitutes and executed call checks - it works, but a bit cumbersome to write and maintain, but still loads better than manually testing complex import flows.
-
I built something useful with the #erlang programming language: a tool to determine whether data found in files spat out by a generator contains information that matches contents of a database. This is used to #unittest the generator. The client for which this got built didn't have automated unit tests for that yet. This should help detect regression bugs caused by maintenance.
-
Code review complete. Time to merge.
Final damage:
[native-aot cdfb42b2] Add Native AOT support
Date: Wed Feb 25 11:16:49 2026 -0800
856 files changed, 33149 insertions(+), 14167 deletions(-) -
New option coming for the xunit3 template: "--native-aot".
This will only be available for C# projects, since Native AOT is only implemented for C#. #DotNet #UnitTest #NativeAOT
-
They may take longer to builder, but they're definitely faster to run. 😄 #DotNet #UnitTest #NativeAOT
-
I'm positive the code generation has holes in it, despite my extensive attempt to ensure I covered all my bases, but... I think I'm ready the merge `native-aot` into `rel/4.0.0` and maybe push a pre-release build soon. #DotNet #UnitTest #NativeAOT
-
The existing xUnit.net analyzers that are errors are helping define the most important set of "did I remember to test for this?" in the code generators, because they almost all end up creating generated code that won't compile (e.g., m Member data pointing at a non-public member). Almost all of the rest inform what conditions need to be validated in the generated code (e.g. incorrect number of values in a data row vs. number of parameters to the test method).
-
Still don't have caching wired up, and I don't think I'm gonna bother, because things definitely got faster.
Also, count-wise I clearly have to make a pass to determine if there are more current "reflection only" tests that need AOT backfills.
Also need to fix an issue where I'm calling tests multiple times if they're defined in a partial across separate files.
-
The tool chest is almost complete!
Typical "Unit tests without integration tests" situation -- since installing the small 'box' in the left, I can't fit my saws underneath anymore.
Argh.
-
Spot check!
Also, the tests run in 0.021s, which is 5x faster than using the JIT. 🎉
-
Tests fixed, and xunit.v3.core.tests restructured for the changes introduced to the runner hierarchy (CoreXyzRunner and associated context inserted between TestXyzRunner and XunitTestXyzRunner, with CodeGenXyzRunner also deriving from CoreXyzRunner).
Now it's time to get the xunit.v3.core.aot.tests building and passing, and add new tests for all the new code (which is significant 😮💨).
-
This morning, I'm adding the missing type coercion support for theory parameters.
I found another one that isn't going to work: `params` parameters for theories. There's no way for us to make the right kind of array at runtime, so we'll have to let you do the "hard work" of putting things in an array for us. Thankfully C#'s `[]` array syntax helper should make this conversion pretty trivial for most people. #DotNet #NativeAOT #UnitTest
-
UnitTesterJS: Lightweight Unit Test Runner for Javascript
Runs test functions while keeping track of failures, logging them and to provide a summary. No dependencies, runs in the browser too. Works well with chai.
new in 2.0.0:
- Adds running all test classes of a (Java|Type)Script module.
- Renames the project from the former creative name LutruJS to something more recognizable.😅features: https://docs.miamao.de/@main/unittesterjs/?#features-and-configuration
https://codeberg.org/harald/unittesterjs -
UnitTesterJS: Lightweight Unit Test Runner for Javascript
Runs test functions while keeping track of failures, logging them and to provide a summary. No dependencies, runs in the browser too. Works well with chai.
new in 2.0.0:
- Adds running all test classes of a (Java|Type)Script module.
- Renames the project from the former creative name LutruJS to something more recognizable.😅features: https://docs.miamao.de/@main/unittesterjs/?#features-and-configuration
https://codeberg.org/harald/unittesterjs -
UnitTesterJS: Lightweight Unit Test Runner for Javascript
Runs test functions while keeping track of failures, logging them and to provide a summary. No dependencies, runs in the browser too. Works well with chai.
new in 2.0.0:
- Adds running all test classes of a (Java|Type)Script module.
- Renames the project from the former creative name LutruJS to something more recognizable.😅features: https://docs.miamao.de/@main/unittesterjs/?#features-and-configuration
https://codeberg.org/harald/unittesterjs -
UnitTesterJS: Lightweight Unit Test Runner for Javascript
Runs test functions while keeping track of failures, logging them and to provide a summary. No dependencies, runs in the browser too. Works well with chai.
new in 2.0.0:
- Adds running all test classes of a (Java|Type)Script module.
- Renames the project from the former creative name LutruJS to something more recognizable.😅features: https://docs.miamao.de/@main/unittesterjs/?#features-and-configuration
https://codeberg.org/harald/unittesterjs -
On the plus side, I now have all of Fact, CulturedFact, Theory, and CulturedTheory running. Theories support InlineData, MemberData, and ClassData. User extensibility for data attributes will require people to write a code generator (kind of a bummer, but that's how all this Native AOT works). #DotNet #NativeAOT #UnitTest
-
Lightweight Unit Test Runner for Javascript
Provides a class UnitTester to run test functions while keeping track of failures, logging them and to provide a summary. It has no dependencies and runs easily in the browser too.
1.2.0 adds a test result logger for HTML element output in the browser (not just console)
https://codeberg.org/harald/lutrujs/
features: http://localhost:8000/lutrujs/index.html#features-and-configuration -
Lightweight Unit Test Runner for Javascript
Provides a class UnitTester to run test functions while keeping track of failures, logging them and to provide a summary. It has no dependencies and runs easily in the browser too.
1.2.0 adds a test result logger for HTML element output in the browser (not just console)
https://codeberg.org/harald/lutrujs/
features: http://localhost:8000/lutrujs/index.html#features-and-configuration -
This definitely changes how extensibility works.
One example: instead of relying on a discoverer and custom test class type for [CulturedFact], we have a custom code generator.
So now I have a FactAttributeGenerator and a CulturedFactAttributeGenerator, and the old reflection-based code (FactAttributeDiscoverer, CulturedXunitTestCase) are unused in native AOT.
-
{testthat} is great for automatic testing. Here are some tricks for the heavy user: https://blog.r-hub.io/2020/11/18/testthat-utility-belt/ #rstats #testing #unittest #testthat
-
Hi #ruby community I'm looking for other recommendation here https://codeberg.org/codeDude/romodoro-socket/src/branch/main/lib/romodoro/socket/timer/countdown.rb
I''m not sure how to test this with #Rspec
basically the intention is test if the duration is for example 2 seconds the countdown spend 2 seconds.
Could you gimme ideas please?
-
New 1.1.0
Lightweight Unit Test Runner for JavaScript --- LutruJS
It got DX (developer experience) improvements: both, test functions and test instances, can be switched off more easily (like you may want during debugging), avoiding hassles with linters/compilers about unused code.
Tell me your preferred name for this package as the current one sounds somewhat awkward.
Features: https://docs.miamao.de/@main/lutrujs/?#features-and-configuration
Project: https://codeberg.org/harald/lutrujs
-
It's just [Fact] tests for now, but I just got an end-to-end run through the code generation path for Native AOT, running all the tests (or not, as needed). 🎉
Also, stack traces? What stack traces? 😂
-
Just now I released 1.0.0
Lightweight Unit Test Runner for JavaScript --- LutruJS
It now allows to fail tests with a timeout. This finishes the initially planned feature set and got us version 1.0.0
A quick feature overview is here: https://docs.miamao.de/@main/lutrujs/?#features-and-configuration
The project: https://codeberg.org/harald/lutrujs
-
Lightweight Unit Test Runner for JavaScript --- LutruJS
We now have 0.9.0 out on #Codeberg, nearly feature complete.
- The main addition is support for async test methods (the reason why I had to rant a bit recently about async🙂)
- A minor addition provides for better logging of parametrized tests
- Sanity check to assure a test class has at least one test.
- Documentation updateshttps://codeberg.org/harald/lutrujs
(Please someone suggest a better name!😩)
-
I could not resist. Now I wrote a minimalist, no-dependency unit test runner for JavaScript. Two motivations:
- the available stuff is monstrous
- I wanted to see how far I get😎Publish early, publish often, so here comes the first cut of the
Lightweight Unit Test Runner for JavaScript
According to my README it is already great for small projects.
https://codeberg.org/harald/lutrujs
#javascript #typescript #unittest #lutrujs
The name, lutrujs, leaves something to be desired.🤪 Suggestions welcome.
-
#JavaScript, such a lovely programming environment
Writing some unit tests for a **browser** app which must parse historic XML (WebDAV result) I stumble upon
ReferenceError: DOMParser is not defined
It would be no problem in the browser itself, but the tests were supposed to run without browser. And node has no DOMParser, I just learned.
No problem, jsdom seems to be the library to go with. But then: https://npm.anvaka.com/#/view/2d/jsdom
45 dependencies😱
-
I spent some time writing up how to #unittest the creation and changing of #sql database components in #Microsoft #SqlServer 's #TSql . It's useful in restricted environments that won't allow other development tools that normally could conduct unit tests.
https://www.patreon.com/posts/148232620
