Diego Molina

Curious about test-driven development? Whether or not your software team practices scrum, TDD can support your team’s agility with a an iterative, incremental, test-first focus. Of course, it has its challenges and may not be right for every team. Explore TDD in this article written by Certified Scrum Alliance Trainer™ Paul Moore.

25

Don't miss 🥋 Gil Zilberfeld TestinGil 🥋 talk at EuroSTAR 2024: "API Test Planning Live!" Dive into the complexity of API testing with an interactive session. Learn how to think differently about API testing. Join this session for insights and practical approaches! https://bit.ly/3On4qzZ

1

🤔 Ever wondered why testing asynchronous architectures is so challenging? In the realm of end-to-end testing, isolating messages within your queue can revolutionize how you approach asynchronous architectures. This article dives deep into the complexities of testing with Signadot, highlighting why message-level isolation can be a game-changer for systems using Kafka, RabbitMQ, and more. Discover how you can streamline your testing processes without the headache of duplicating entire queues or creating new topics. Check out the full article 👉https://hubs.li/Q02FtPnW0 #SoftwareTesting #Kafka #AsynchronousArchitecture #TechInnovation #Signadot #EventDriven

1

Yuriy Prykhodko (AWS) recently shared an article by ThoughtWorks about the CUDOS Dashboard. Summary: "Our advice has always been to monitor costs as a fitness function." The analogy to fitness is a very apt one - as Yuriy has said, "FinOps as a process." Just like you cannot do a single mega workout and then be fit, you cannot do a single cost-optimization exercise. What is needed is continuous monitoring and work to keep things optimized. There is always entropy in your AWS account - resources become idle, new technologies (e.g. Graviton 4) become available, etc. Check the comments for a link to the ThoughtWorks article, and also for an AWS Made Easy Episode with Yuriy.

Jikken v0.7 Released! What's new? Jikken can now generate test files from OpenAPI specs! We also now support JUnit output for better integration with your existing CI/CD dashboards. But that's not all, we've also introduced an official VSCode plugin to help write your tests. Check out our blog post for more details on these features, and more, which came out with v0.7. What is Jikken? Jikken is an open-source CLI tool for automated API testing, built in Rust! The tool was originally developed to help validate complex data APIs used for analytics dashboards. Jikken leverages a declarative YAML test format for defining complex test scenarios. This means the tests are self-documenting, and they're easy to write for Devs, QA, and Ops teams alike! And since it's file-driven, Jikken integrates extremely well with both source control and CI/CD systems. What should you expect in v0.8? We're working on more variable generators (fuzz testing), parallel test execution (performance/load testing), and improvements to our OpenAPI spec ingestion. Don't forget to star us on GitHub so you can stay up-to-date on the latest releases: https://lnkd.in/gMpt3k-4.

15

Shifting Left: Evolving QA in Modern Dev Teams 🔄 Explore the latest installment in our series on shifting testing left! QA has seen it all, from being the final stamp of approval to teams proudly declaring they don't need it. As we shift testing left, giving product teams more responsibility, the big question is: who should own tests? 🤔 Join us as we delve into how integrating QA within teams boosts code quality and streamlines development. 🚀 Read here: https://hubs.ly/Q02BLBVR0 #SoftwareTesting #ShiftLeft #QA #Microservices #DevOps #DeveloperExperience #TestingStrategies

2

Great article from Uber’s engineering blog on their Short-Lived Application Testing Environments (SLATE), the internal tooling that they use to run their entire test suite on-demand. It’s a fascinating inside look at how they’re able to build and test at their scale. To get reliability and velocity in your release process, you need to start from the ground up. Much of this boils down to dev/staging/prod parity: "An E2E test for a service should run against the same version of dependencies as deployed in production for correctness." We’re big fans of this type of pre-production infrastructure, after all, this is what we do at Shipyard. If you want to build like Uber, you can have your very own SLATE 🏗 https://lnkd.in/gQ2qDDc5 #devops #platformengineering #devex #testautomation

5

1 comentario