mastodon.zunda.ninja is one of the many independent Mastodon servers you can use to participate in the fediverse.
Zundon is a single user instance as home of @zundan as well as a test bed for changes of the code.

Administered by:

Server stats:

1
active users

#testing

0 posts0 participants0 posts today

A piece of criticism to all code forges I know: why not run #CI on all commits?

A bad commit is a liability. It will break bisect and make debugging miserable.

#ForgejoActions takes it to the extreme and cancels an already running action when I push another change.

I get it - it's too slow and expensive to test them all when pipelines take minutes to run. But you could just pause the old ones until the newest one is finished!

One of the (many) challenges in #testing the #Fediverse is that some of the standards say one thing, but what is widely implemented is another.

Example: RFC 7033, WebFinger, section 5, requires presence of a CORS header.

So far we've not seen any Fediverse application that actually does this. Arguably it's not needed in the Fediverse, but the standard says MUST.

So we can either have all applications fail that test or not test against the standard. Your thoughts?

rfc-editor.org/rfc/rfc7033#sec

www.rfc-editor.orgRFC 7033: WebFinger

There is a new #job opportunity at #OpenVPN for a #automation #QA role

careers.openvpn.net/o/core-aqa

We want to expand our Core team (developing the "lower level" components of the OpenVPN stack) to become even better at testing our low-level C++ code.

Currently we target #cpp17 and will move forward as compilers improve across all supported platforms.

Feel free to reach out if you have any questions!

OpenVPNCore AQA Engineer (C++)We are looking for a seasoned Automation QA with a keen eye for detail, a passion for testing, and an eagerness to contribute to our product. The Core team at OpenVPN Inc. is responsible for technolog

🚀 Unveil the Power of the NixOS Integration Test Driver! In Part 1 of our series, we dive deep into this incredible tool that's changing the game in DevOps and software testing. From orchestrating multiple VMs to running GUI apps with text recognition, discover how it simplifies integration testing and saves you precious time and resources.

Developers and system administrators, this one's for you! In a world where efficiency and reliability are paramount, the NixOS Integration Test Driver combines the best of declarative configuration, virtualization, and Python scripting. It's a hidden gem within the NixOS ecosystem that's set to revolutionize the way we test and validate our systems.

Whether you're a seasoned NixOS enthusiast or new to this innovative operating system, fasten your seatbelts as we venture into a world where integration testing becomes an effortless and integral part of your development and deployment process.

In this article, you'll explore:
✅ Minimal requirements: Accessible to a wide range of developers with just a Linux system and KVM support.
✅ Effortless debugging: Run tests locally for debugging when integration tests fail in your CI pipeline.
✅ Speed and reliability: Unparalleled framework for creating robust tests that don't flake.
✅ Realistic simulations: Closely simulate actual customer deployments, enhancing your ability to catch issues before they reach production.

Stay tuned for Part 2, where we'll dive even deeper into the NixOS Integration Test Driver!

➡️ nixcademy.com/2023/10/24/nixos

Continued thread

If you want to help with this, please join #testing:grapheneos.org on Matrix. Support for the Pixel Fold will come soon but we don't have access to the device ourselves yet and are missing testers as a substitute for that. We can likely finish adding support quickly.

Chromium still has some problems with automated end-to-end tests on Linux Wayland - for example, not being able to control window size and position without user interaction breaks some tab dragging tests that need two windows of a given size to be right next to each other.

We're already working around other limitations with a custom test protocol extension, but in this case, it seems easier to just emulate the user interaction needed to move and resize the windows! It's not as trivial as it might seem, mostly due to client-side decorations messing up the window bounds calculations, but I managed to get a first prototype working 😄

Continued thread

... and here it is passing all its feature tests like a good little service. 😍

In total there are:
🔸 77 unit tests
🔸 32 feature tests
🔸 12 integration tests

The left hand side shows the server itself, and the right side is local.

I'm pretty pleased with the patterns I've built - each deployment must pass unit and feature tests as a part of build before it can be deployed.