mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,5 Tsd.
aktive Profile

#Unittest

1 Beitrag1 Beteiligte*r0 Beiträge heute

The amount of difficulty in making the @xunit assertion library work in Native AOT has me thinking about whether it needs a complete redesign for those types of projects.

Trying to shove 50 things into `Assert.Equal` and figure out what you meant at runtime is definitely not the right design for AOT. It's not necessarily a great design at all, but there's where it's been for 18 years.

Given that xUnit.net runs tests in random order by default, would changing the randomization order (in order to fix a bug) just be considered a bug fix or a breaking change?

Asking for a SemVer.

Fortgeführter Thread

Just a reminder that we only have roughly 10 more days of before we ship 3.0. If you've been putting off validating your tests and/or extensions with the latest prerelease, your time is running low...

#DotNet#CSharp#FSharp

une bibliothèque pour mocker les ressources #AWS utilisées dans le code de production #Python que vous testez (S3, par exemple) : github.com/getmoto/moto

La page github.com/getmoto/moto/blob/m documente comment écrire les tests (#pytest, #unittest) et donne quelques conseils pour écrire du code de production plus facile à tester (en ce qui concerne les interactions avec boto3, le client vers les services AWS).

GitHubGitHub - getmoto/moto: A library that allows you to easily mock out tests based on AWS infrastructure.A library that allows you to easily mock out tests based on AWS infrastructure. - getmoto/moto

So made a source generator - ended up rather complex.
But I find unit testing it very tedious when verifying the generated output via Verify.

Is it not possible to load a class/instance as source in the testing, and use it as foundation for the generator. Instead of having to manually writing (and maintaining) the source as a string to then parse into a syntax tree to verify output? I mean it can generate on compile time, so why not at test? :D

As it turns out, there were some fundamental problems with the testing-strategy I had in mind for testing the PACT processes. That is, problems with how I'd planned to implement those tests, not with which tests needed to be implemented (at least not yet). Those issues took a bit of thinking through, and there were some interesting results from related investigation.

#UnitTest #Python

goblinfish-code.blogspot.com/2

goblinfish-code.blogspot.comWhen not to mock or patchDespite taking a break from working on the unit test stubs for the goblinfish-testing-pact package , it hasn’t been far from my thoughts, f...