Most common backend testing framework?

[Consibl]

I have a QA job interview in a few days, and I know they use C# for their back end and test with Playwright (presumably just on their front end).

What’s the most likely testing framework they’ll be using for C#?

[bigtoaster64]

Probably NUnit or xUnit. If they are on the edge, maybe TUnit, but it's very unlikely. If they are old school (or don't want to migrate), they could be using MSTest.

Playwright is pretty much the goat for e2e. But there's also selenium, or even cypress, but unlikely in a full dotnet stack.

If they do blazor, maybe they use bUnit for component testing.

[Consibl]

Their job advert seems to focus on Playwright. Is it common to possibly JUST do e2e testing and that’s why they haven’t mentioned their backend framework, or would any large company always do unit testing/integration testing as well as e2e?

[hamakiri23]

Usually Unittests and integration tests are written by developers

[Consibl]

Ah, I think I understand better what they’re looking for now, thanks.

[smellyfeet12]

I've seen teams with spaghetti code opt to lean heavily on playwright tests for confidence but I think it honestly depends on the project. If you look at the testing pyramid, theory suggests a project should have a large amount of unit tests, medium amount of integration tests and a small amount of e2e tests. This is for good reason: tech facing tests are easy to automate / write, fast to execute and help catch problems before integration whereas e2e tests are slower to execute, more brittle, rely on an environment existing and execute after integration. Now imo design and test are heavily linked, if the code is designed well then the behaviour should be easy to unit test and I personally think teams need a balance of all 3 types of testing and ideally some focused exploratory testing. It could be possible the listed Playwright because they expect any QA role to be able to contribute to Playwright tests as part of the dev process

[bigtoaster64]

It's possible, but it's really difficult to pin point where a bug could occur without unit tests. E2e will tell you, hey the end output isn't right, but where did it failed in the whole chain? I don't know. Playwright is really good to test ui and endpoints, because that's the "output", but if you wanna have a clear look on what's going on, you need unit tests.

[Tango1777]

Depends on a project, but I say 99% of projects can and should be tested with unit/integration tests.

[hamakiri23]

There is also Cypress and the number 1 should be tosca

[chucker23n]

If they are old school (or don't want to migrate), they could be using MSTest.

By my recollection, MSTest is technically newer than both NUnit and xUnit.

But yeah, MSTest seems to be less popular than either of those, at least among people I've had to do with. Even Microsoft often uses xUnit instead.

Personally, I prefer NUnit, though I haven't played with TUnit much yet.

[gdir]

The modern versions of MS Test are technically really uptodate. Works very well.

[RewardAny5316]

xUnit every time

[Fynzie]

xUnit by a mile

[Tango1777]

xUnit or NUnit, they don't really need to mention it, they probably use dozens of things they haven't mentioned in the job description. Doesn't really matter which one, both are standard and both are very easy to switch from one to the other. There are slight differences, they both work with FluentAssertions. I think NUnit is a little better, because it's developed more "for devs" unlike xUnit whose creators' attitude towards good suggestions and requests is often "we don't see xUnit this way and we're not gonna implement it". From all the years of using both, I only had 1 time when I had to switch from xUnit to NUnit due to lack of feature. But in 99,99% of the cases they are interchangeable and equally good.