leanpub, to Java
@leanpub@mastodon.social avatar

Testing Spring Boot Applications Demystified by Philip Riecks is free with a Leanpub Reader membership! Or you can buy it for $9.00! http://leanpub.com/testing-spring-boot-applications-demystified

adamchainz, to python
@adamchainz@fosstodon.org avatar

✍️ New post with a testing tip for mocking inner imports.

https://adamj.eu/tech/2024/05/17/python-mock-inner-import/

adamchainz, to python
@adamchainz@fosstodon.org avatar

A pattern I’ve recently enjoyed using:

  1. Change some function in a way that needs fixes to call sites.
  2. Run the whole test suite with pytest.
  3. Copy the list of failing test IDs from pytest’s summary into a scratch file.
  4. Fix up the found callers.
  5. Verify everything fixed by saving the list of tests with: pytest $(cat scratch/testids.txt)

watte,
@watte@norden.social avatar

@adamchainz like --lf but without excluding successful tests the next time? Seems nice :)

adamchainz,
@adamchainz@fosstodon.org avatar

@watte Yes, and allowing partial test runs in step four whilst fixing up certain callers.

leanpub, to Java
@leanpub@mastodon.social avatar

Testing Spring Boot Applications Demystified by Philip Riecks is free with a Leanpub Reader membership! Or you can buy it for $9.00! http://leanpub.com/testing-spring-boot-applications-demystified

leanpub, to Java
@leanpub@mastodon.social avatar

Testing Spring Boot Applications Demystified by Philip Riecks is free with a Leanpub Reader membership! Or you can buy it for $9.00! http://leanpub.com/testing-spring-boot-applications-demystified

zwovierzwo, to debian

Mal eine Frage in die Gemeinschaft.
Vor längerer Zeit hatte ich Mal eine Anleitung wie man in ein #Debian stable einbaut das manche (nicht alles) Pakete aus dem #Testing oder #unstable installiert werden. Mit allen Risiken ich weiß.

Leider finde ich die nicht mehr.
Hat hier jemand einen Tipp 🤔

Danke schon mal

LateNightLinux, to linux
@LateNightLinux@mastodon.cloud avatar

Andy is a huge proponent of test-driven development and explains why – including types of code testing including unit tests and integration tests, when you actually need to run tests, how long they should take, and more.

https://www.linuxdevtime.com/linux-dev-time-episode-97/

coulrophobia,
@coulrophobia@mastodon.social avatar

@LateNightLinux I have been listening to Late Night Linux for quite a long time, excellent, the presenters have a magical working combination, this beats anything on commercial outlets, keep up the good work!

JoeRess,
@JoeRess@fosstodon.org avatar

@coulrophobia @LateNightLinux thanks for the kind words and thanks for listening!

bmispelon, to django
@bmispelon@mastodon.social avatar
josh,
@josh@joshthomas.dev avatar

@ghickman @webology @benjaoming @bmispelon On top of the fact that if you really need or miss the factory pattern, there are Recipes within model-bakery that can do that for you as well

ghickman,
@ghickman@mastodon.social avatar

@josh @webology @benjaoming @bmispelon that's a really useful comparison, thank you!

predrag, to rust
@predrag@hachyderm.io avatar

cargo-semver-checks now adds the latest Rust to its CI test matrix automatically 🤩

I love automating repetitive maintenance work, and Rust 1.78 is a great real-world test case to make sure this new automation works properly. It did!
https://github.com/obi1kenobi/cargo-semver-checks/pull/773

henrikjernevad, to programming
@henrikjernevad@mastodon.social avatar

Why should you unit test? What should you unit test? And how much?

Today's blog post answers these questions and provides some helpful guidelines.

The post is actually a lightly edited extract of a book on unit testing that I started about 10 years ago but never finished. Still, it has aged reasonably well.

https://henko.net/blog/why-write-unit-tests/

underlap,
@underlap@fosstodon.org avatar

@henrikjernevad I really enjoyed your post and thought it deserved a response. https://underlap.org/why-write-unit-tests

bluGill,
bluGill avatar

@henrikjernevad Every test you listed there is the type that should be deleted when you are done.

Which is to say you are missing something critical: to ensure when someone in the future makes a change they don't introduce bugs. Any test that will never alert you to a bug in your code by failing should not be kept. (that is about 80% of all tests, but I don't know how to figure out the difference)

leanpub, to Software
@leanpub@mastodon.social avatar

A Practical Guide to Testing in DevOps by Katrina Clokie is free with a Leanpub Reader membership! Or you can buy it for $7.99! http://leanpub.com/testingindevops

mzikmund, to VisualStudio
@mzikmund@dotnet.social avatar

🌐 Ever wished you could share your localhost web app with the world? With Dev Tunnels, now you can! Check out my latest video to see how:

https://youtu.be/6IrPc3zU1ho

mglaman, to drupal
@mglaman@phpc.social avatar
henrikjernevad, to programming
@henrikjernevad@mastodon.social avatar

I think that testable code is reusable code. When you test a function, you run the code in another context than it was built for (the production code). If your code is not reusable you will feel that pain in your tests.

This blog post gives an example of how getting side effects out of functions make them both easier to test and reuse.

https://henko.net/blog/testable-code-is-reusable-code/

underlap,
@underlap@fosstodon.org avatar

@henrikjernevad Nice example of the single responsibility principle too.

WebAxe, to accessibility
@WebAxe@a11y.info avatar
  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • thenastyranch
  • magazineikmin
  • cubers
  • InstantRegret
  • cisconetworking
  • Youngstown
  • vwfavf
  • slotface
  • Durango
  • rosin
  • everett
  • kavyap
  • DreamBathrooms
  • provamag3
  • mdbf
  • khanakhh
  • modclub
  • tester
  • ethstaker
  • osvaldo12
  • GTA5RPClips
  • ngwrru68w68
  • Leos
  • anitta
  • tacticalgear
  • normalnudes
  • JUstTest
  • All magazines