Hurl is a command-line tool for running and testing HTTP requests using a plain text format. It supports chaining requests, capturing values, and evaluating queries across various API types (REST, SOAP, GraphQL) and formats (XML, JSON). Hurl is lightweight, efficient, and integrates well with CI/CD pipelines, offering features like response assertions, cookie management, and performance testing. It is built on Rust and powered by libcurl, ensuring fast and reliable HTTP operations.
Extreme TLDR:
Test-driven development (TDD) can frustrate newcomers due to its perceived rigidity. The key issues include overly strict adherence to the “Red-Green-Refactor” cycle without recognizing individual skill levels or situational pressures. Developers should see TDD as a flexible practice rather than a strict procedure. Practical tips to begin TDD include brainstorming tests, organizing code into pure functions, acknowledging imperfect test coverage, avoiding direct reliance on externally owned code, using wrappers, employing dependency injection, and keeping UI handling simple and abstract. The aim is continuous practice and improvement rather than perfection. Readers with a basic understanding of JavaScript and React may find the article particularly beneficial.
https://8thlight.com/insights/getting-started-tdd-practical-guide
Automated visual regression testing with Playwright allows for easier comparison of visual artifacts on websites. The author aims to refactor CSS for better structure and dark mode functionality while fearing bugs from large changes. Playwright's snapshot testing can facilitate this by taking screenshots to compare against a baseline, though it can be slow and sensitive to various factors. The setup involves configuring Playwright and creating a dedicated test directory, with a focus on capturing the entire page rather than just the viewport. A site map generator allows for dynamic test creation, and custom CSS can help mitigate flakiness in visual comparisons. Overall, while the process is complex, it addresses the need for reliable testing during development.
https://css-tricks.com/automated-visual-regression-testing-with-playwright/
Test-first development is challenging because it requires deep thinking and planning before coding, which many programmers avoid to quickly ship products. Emphasizing speed over quality leads to poor development practices, like Test-Last Development, where testing is an afterthought. This approach may deliver immediate results and satisfy management but undermines long-term product reliability. Ultimately, the article critiques the industry's focus on short-term gains at the expense of testing and quality assurance.
https://jarosz.dev/atomicessay/why-test-first-development-is-so-damn-hard/
