<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/tags/testing/best-of/2025" -->

---
title: Best Testing posts of 2025 | daily.dev
description: The most upvoted Testing posts of 2025, curated by the daily.dev community.
canonical: https://daily.dev/tags/testing/best-of/2025
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:url: https://daily.dev/tags/testing/best-of/2025
og:type: website
og:site_name: daily.dev
og:title: Best Testing posts of 2025 | daily.dev
og:description: The most upvoted Testing posts of 2025, curated by the daily.dev community.
og:image: https://media.daily.dev/image/upload/s--VAY5ToZt--/f_auto/v1724209435/public/daily.dev%20-%20open%20graph
---

# Best of Testing — 2025

1. 1  
[](/posts/the-crash-landing-of-vibe-coding-8crisdutx "The Crash Landing of Vibe Coding")  
Article  
![Avatar of khokbmumuz4w1vbvtnmld](https://media.daily.dev/image/upload/s--XETtmu2---/f_auto/v1768495176/avatars/avatar_kHOkBMuMUz4W1VBvtNmLd?_a=BAMAMiiu0)Claudette · 1y  
The Crash Landing of Vibe Coding  
Vibe coding, while potentially speeding up initial development, often leads to significant problems when projects encounter real-world challenges. The approach typically fails in areas like scalability, debugging, and testing, ultimately causing more harm than good. Developers should prioritize proper software engineering practices over quick shortcuts to avoid costly technical debt and project failures.  
372  
49
2. 2  
[](/posts/ep151-24-good-resources-to-learn-software-architecture-in-2025-nrzofimde "EP151: 24 Good Resources to Learn Software Architecture in 2025")  
Article  
![Avatar of bytebytego](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/35be29234ee14d01a9cd049c52e12753)ByteByteGo · 2y  
EP151: 24 Good Resources to Learn Software Architecture in 2025  
ByteByteGo Newsletter shares 24 valuable resources for learning software architecture in 2025, including books, tech blogs, YouTube channels, and whitepapers. It also compares API styles (SOAP vs REST vs GraphQL vs RPC) and AWS services (SQS vs SNS vs EventBridge vs Kinesis). Additionally, it outlines methods to enhance API performance and introduces Grok-3, a powerful AI developed by xAI.  
313
3. 3  
[](/posts/how-to-become-a-confident-software-engineer-0sqq4kapt "How to Become a Confident Software Engineer")  
Article  
![Avatar of francofernando](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/2a66d4e9f17e4214a6d620baed8123e1)The Polymathic Engineer · 1y  
How to Become a Confident Software Engineer  
Building confidence as a software engineer requires a structured approach focusing on six key areas: mastering one programming language deeply, writing unit tests with continuous integration, making refactoring a regular habit, pairing with other developers, reading technical books thoughtfully, and teaching others what you learn. The author emphasizes that understanding fundamentals in one language transfers to others, unit tests provide safety nets for bold changes, clean code through refactoring improves maintainability, pairing accelerates learning through different perspectives, quality books teach thinking patterns beyond tutorials, and teaching solidifies understanding while helping others.  
305  
13
4. 4  
[](/posts/stop-using-typescript-s-exclamation-mark-re1atfub4 "Stop Using TypeScript's Exclamation Mark")  
Article  
![Avatar of typescripttv](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/57ce30b9764a474caf60a5b81549c1b3)TypeScript.TV · 43w  
Stop Using TypeScript's Exclamation Mark  
The non-null assertion operator (!) in TypeScript bypasses type safety by forcing the compiler to treat potentially nullable values as non-null, leading to runtime crashes. Instead of using this operator, developers should employ safer alternatives: optional chaining for nested property access, nullish coalescing for default values, conditional operators for explicit branching, type guards for reusable validation, and assertion functions for enforcing invariants. These approaches maintain type safety while handling null and undefined values appropriately, following fail-fast principles and preventing silent failures.  
258  
16
5. 5  
[](/posts/before-refactoring-hmjgdgpd5 "Before refactoring")  
Article  
![Avatar of francofernando](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/2a66d4e9f17e4214a6d620baed8123e1)The Polymathic Engineer · 1y  
Before refactoring  
Refactoring code requires careful preparation and the right mindset to avoid common pitfalls. Key considerations include understanding the existing codebase thoroughly, resisting the urge to rewrite everything from scratch, making incremental changes, preserving existing tests, checking your motivations for refactoring, evaluating technology changes carefully, and accepting that refactoring projects can sometimes fail. The difference between successful and failed refactoring often comes down to proper planning and approach rather than technical skill alone.  
190  
5
6. 6  
[](/posts/this-is-what-shipping-without-tests-looks-like-c2yvouqfh "This Is What Shipping Without Tests Looks Like")  
Article  
![Avatar of zerotomastery](https://media.daily.dev/image/upload/s--TO8V2btR--/f_auto/v1739806832/squads/1ee5eb72-76c0-4c3e-90ec-1896c96950d8)Zero To Mastery · 1y  
This Is What Shipping Without Tests Looks Like  
185  
15
7. 7  
[](/posts/storybook-9-4zjkvk4qn "Storybook 9")  
Article  
![Avatar of storybook](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/f9bec4fb151c4b73a6f736d89bace27e)Storybook · 1y  
Storybook 9  
Storybook 9 introduces comprehensive component testing capabilities powered by Vitest and Playwright. The release features interaction tests, accessibility testing, visual regression testing, and coverage reports all integrated into a unified testing experience. Key improvements include a 48% smaller bundle size, story generation tools, tag-based organization, and story-level globals. Framework updates include Vite-powered Next.js support, Svelte 5 compatibility, and enhanced React Native integration.  
181  
8
8. 8  
[](/posts/my-llm-coding-workflow-going-into-2026-vi9oycjke "My LLM coding workflow going into 2026")  
Article  
![Avatar of elevate](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/9f405475ad274b7a9cdc345c6b357107)Elevate · 42w  
My LLM coding workflow going into 2026  
A comprehensive guide to using LLM coding assistants effectively in 2026\. Key practices include starting with detailed specifications before coding, breaking work into small iterative chunks, providing extensive context to the AI, choosing appropriate models for different tasks, maintaining human oversight through testing and code review, committing frequently for version control safety, customizing AI behavior with rules and examples, leveraging automation as quality gates, and treating AI as a force multiplier rather than replacement. The workflow emphasizes treating LLMs as junior pair programmers requiring guidance while maintaining developer accountability for all code produced.  
176  
5
9. 9  
[](/posts/dopamine-driven-development-tyla1nofx "Dopamine Driven Development")  
Video  
![Avatar of bigboxswe](https://media.daily.dev/image/upload/s--KMRj-zRu--/f_auto/v1711188128/logos/bigboxswe)bigboxSWE · 1y  
Dopamine Driven Development  
A developer shares how leveraging small dopamine rewards from visual feedback can make coding more enjoyable and productive. The approach involves customizing development tools like terminals, setting up CI/CD pipelines, writing tests, and using task managers to create satisfying visual cues that motivate continued coding. The concept suggests that making development environments more engaging through animations and visual feedback can help overcome coding burnout and increase productivity.  
171  
8
10. 10  
[](/posts/postman-is-logging-all-your-secrets-and-environment-variables-0rzc8mjia "Postman is logging all your secrets and environment variables")  
Article  
![Avatar of lobsters](https://media.daily.dev/image/upload/s--tl8v_Fku--/f_auto,t_logo/v1698841318/logos/lobste.jpg)Lobsters · 1y  
Postman is logging all your secrets and environment variables  
Postman has been found to log secret strings and environment variables, compromising user privacy. Despite claims of protecting sensitive data, the app sends unmasked variables to its servers, posing risks especially for healthcare applications. Users are advised to block Postman's analytics endpoints to prevent data leakage.  
168  
34
11. 11  
[](/posts/applied-software-engineering-at-google--7e87dtdbc "Applied "Software Engineering at Google"")  
Article  
![Avatar of elevate](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/9f405475ad274b7a9cdc345c6b357107)Elevate · 2y  
Applied "Software Engineering at Google"  
Google's software engineering practices provide valuable insights that can be adapted by organizations of any size. Key principles include cultivating a comprehensive testing culture with automated tests, establishing effective code review processes, maintaining thorough documentation, fostering knowledge sharing, managing dependencies wisely, using progressive rollouts and feature flags, refining incident response procedures, proactively managing technical debt, prioritizing psychological safety in teams, and leveraging AI to enhance software engineering. Understanding the 'why' behind these practices and starting with small, impactful changes can help build a strong engineering culture focused on quality and continuous improvement.  
159  
2
12. 12  
[](/posts/write-unit-tests-don-t-waste-our-money--avy3pgrlo "Write Unit Tests, Don't Waste Our Money!")  
Article  
![Avatar of yegor256](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/e403368e462f4ae184ab876bda3d013d)Yegor's Blog · 1y  
Write Unit Tests, Don't Waste Our Money!  
Automated tests serve as a warranty system that protects business investments in code. When developers write code without tests, they risk breaking previously fixed functionality, essentially wasting employer money on repeated fixes. Test coverage ensures that paid-for code continues working during refactoring and modifications, making it a crucial business protection rather than just a development practice.  
150  
15
13. 13  
[](/posts/maestro-aztne232r "Maestro")  
Article  
![Avatar of community](https://media.daily.dev/image/upload/t_logo,f_auto/v1655817725/logos/community)Community Picks · 1y  
Maestro  
Maestro is an end-to-end testing platform for mobile and web applications that simplifies test creation through visual element inspection and AI assistance. The platform features Maestro Studio for interactive test generation, MaestroGPT for AI-powered command creation, and aims to address the quality control bottleneck in modern software development where AI has accelerated development velocity.  
147  
2
14. 14  
[](/posts/unit-test-a-rest-api-everything-you-need-to-know-rk5z44iuw "Unit Test a REST API? Everything You Need to Know")  
Article  
![Avatar of testimio](https://media.daily.dev/image/upload/s--GP64-U0E--/f_auto/v1719004093/logos/testimio)Testim.io · 2y  
Unit Test a REST API? Everything You Need to Know  
Learn the importance of proper testing in building high-quality REST APIs and discover the three key types of automated tests you should have in your test suite: unit tests, integration tests, and UI tests. Understand the role of each test type and how to implement them effectively to ensure your application remains stable and bug-free through continuous changes and refactoring.  
146  
2
15. 15  
[](/posts/what-to-look-for-in-code-reviews-i4wijdmsu "What to Look for in Code Reviews")  
Article  
![Avatar of francofernando](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/2a66d4e9f17e4214a6d620baed8123e1)The Polymathic Engineer · 1y  
What to Look for in Code Reviews  
A comprehensive guide covering the essential aspects of effective code reviews, prioritized by importance. Covers design considerations as the most critical factor, followed by functionality review, complexity assessment, test quality evaluation, naming and documentation standards, and style consistency. Emphasizes the importance of structured approaches over random scanning, focusing on catching bugs, improving code quality, and facilitating team learning through systematic review practices.  
136  
5
16. 16  
[](/posts/testing-is-software-engineering-9un4ckzn6 "Testing is software engineering")  
Article  
![Avatar of thoughbot](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/9fe12feb57f944a29ff63a79e350081a)thoughbot · 42w  
Testing is software engineering  
Testing should be treated as a core engineering practice, not an afterthought. Writing tests early improves code design by providing immediate feedback on interfaces, enables confident refactoring through reliable CI checks, and facilitates collaboration by uncovering edge cases and serving as living documentation. Tests that are hard to write often signal poorly designed code. Integrating testing throughout development leads to better software design, reduced stress when making changes, and earlier discovery of hidden requirements.  
129  
6
17. 17  
[](/posts/tdd-is-more-important-than-ever-hoeecbmpk "TDD is more important than ever")  
Article  
![Avatar of searls](https://media.daily.dev/image/upload/s--1lBNu4OS--/f_auto/v1756384015/logos/searls)Justin Searls · 46w  
TDD is more important than ever  
Test-driven development skills are becoming critical for working effectively with AI coding agents. Developers experienced in TDD are both the most skeptical of AI code generation and the most successful at using it, because they understand how to build verification into workflows. AI agents, like human developers, need independent ways to verify their work—without verification, they resort to guessing, which compounds errors rapidly. The ability to establish automated testing and verification mechanisms, once a hallmark of agile practices, is now essential for enabling AI agents to produce reliable code through reinforcement learning.  
118  
8
18. 18  
[](/posts/5-best-open-source-tools-for-cross-browser-css-testing-svvgm21bp "5 best open source tools for cross-browser CSS testing")  
Article  
![Avatar of logrocket](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/logrocket)LogRocket · 1y  
5 best open source tools for cross-browser CSS testing  
Cross-browser CSS testing ensures consistent rendering across various browsers like Chrome, Firefox, Safari, and Edge. Tools such as Playwright, Selenium WebDriver, PostCSS and Stylelint, BrowserStack, and BackstopJS automate this process. Playwright and Selenium help with functional testing, PostCSS and Stylelint ensure CSS quality, BrowserStack captures screenshots, and BackstopJS detects visual differences. These open source tools streamline debugging and improve user experience.  
118  
2
19. 19  
[](/posts/storybook-10-i8dytibvp "Storybook 10")  
Article  
![Avatar of storybook](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/f9bec4fb151c4b73a6f736d89bace27e)Storybook · 48w  
Storybook 10  
Storybook 10 transitions to ESM-only, reducing install size by 29% while adding module automocking for easier testing, typesafe CSF Factories for React, tag filtering exclusion for sidebar management, and Svelte async component support. The release includes support for Next 16 and Vitest 4, plus experimental features like test syntax and React Server Component testing. The breaking change requires Node 20.16+, 22.19+, or 24+.  
113  
1
20. 20  
[](/posts/your-job-is-to-deliver-code-you-have-proven-to-work-xeabx8mtw "Your job is to deliver code you have proven to work")  
Article  
![Avatar of simonwillison](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/cf12b897300740218b35f49a6309ec5b)Simon Willison · 42w  
Your job is to deliver code you have proven to work  
Software engineers must deliver proven, working code rather than untested contributions. This requires both manual testing (seeing the code work yourself, documenting steps, testing edge cases) and automated testing (bundling tests with changes). With AI coding agents like Claude Code, developers should train these tools to prove their changes work through testing before submission. The human developer remains accountable for ensuring code quality and providing evidence that changes function correctly.  
112  
12
21. 21  
[](/posts/unnecessary-anxiety-in-software-development-lko0ht4bi "Unnecessary Anxiety in Software Development")  
Article  
![Avatar of simplethread](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/82c0dd537790449d9b595be436d10e7e)Simple Thread · 1y  
Unnecessary Anxiety in Software Development  
Software development often creates unnecessary anxiety through risky practices like deploying without proper safeguards. Using a metaphor of walking across a plank between buildings, the author explains how anxiety is self-reinforcing and leads to avoidance behaviors. Organizations can reduce developer stress by implementing better testing, staging environments, documentation, and blameless cultures. Individuals can combat anxiety by approaching feared tasks, building competence, and accepting discomfort as part of growth. The key is lowering both the likelihood of failure and its consequences.  
108  
5
22. 22  
[](/posts/ai-writes-good-tests-actually-awodep3z3 "AI writes good tests, actually")  
Article  
![Avatar of swizec](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/a0733daf6e014e23a638ded7f2d4cd70)swizec.com · 2y  
AI writes good tests, actually  
Using AI, specifically Cursor, to write tests can be surprisingly effective. It assists in generating tests based on code comments and intent, identifying bugs, and iterating input combinations. This automation helps focus on creating meaningful input scenarios rather than writing and managing tests manually, making the testing process more efficient and insightful.  
107  
6
23. 23  
[](/posts/3-skills-every-early-career-engineer-needs-eqmu12pmd "3 skills every early-career engineer needs")  
Video  
![Avatar of googledevelopers](https://media.daily.dev/image/upload/s--jj3nxRoG--/f_auto/v1725035497/logos/googledevelopers)Google for Developers · 43w  
3 skills every early-career engineer needs  
Early-career software engineers should focus on three fundamental skills: writing clean, maintainable code with meaningful names and simple logic; developing a quality mindset through comprehensive testing that prevents regressions and enables confident refactoring; and mastering essential tools like version control, debugging techniques, documentation practices, and communication skills. These foundational practices create long-term career success more effectively than chasing the latest frameworks.  
102  
2
24. 24  
[](/posts/how-i-use-ai-agents-to-write-code-onvlmqy00 "How I use AI agents to write code")  
Article  
![Avatar of nolanlawson](https://media.daily.dev/image/upload/s--hCPaPAOM--/f_auto/v1727446484/logos/nolanlawson)Read the Tea Leaves · 41w  
How I use AI agents to write code  
A developer shares practical strategies for using AI coding agents effectively after transitioning from skepticism to adoption. Key recommendations include creating comprehensive CLAUDE.md files for project context, using automated tests as feedback loops, running separate AI sessions for code review to catch bugs, and leveraging agents for overnight work on side projects. The author acknowledges AI's limitations with UI work and novel projects, describes the shift toward an architect-like role focused on specs and review, but maintains reservations about using AI for open-source contributions due to ownership concerns.  
99  
3
25. 25  
[](/posts/small-repo-high-quality-lzy61mr2i "Small Repo, High Quality")  
Article  
![Avatar of yegor256](https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/e403368e462f4ae184ab876bda3d013d)Yegor's Blog · 47w  
Small Repo, High Quality  
Breaking software into smaller repositories instead of using monolithic repos improves code quality through stricter style enforcement, deeper testing, more thorough code reviews, better documentation, faster release cycles, improved AI agent effectiveness, quicker onboarding, stronger code ownership, and easier open-source adoption. While companies like Google and Facebook favor monorepos for reduced integration overhead, smaller repositories enable teams to maintain higher quality standards across multiple dimensions of software development.  
99  
11

[See all Testing archives](/tags/testing/best-of)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@graph":[{"@type":"CollectionPage","@id":"https://daily.dev/tags/testing/best-of/2025#page","url":"https://daily.dev/tags/testing/best-of/2025","name":"Best Testing Posts of 2025","description":"The most upvoted Testing posts of 2025, curated by the daily.dev community.","isPartOf":{"@type":"WebSite","url":"https://daily.dev"}},{"@type":"ItemList","@id":"https://daily.dev/tags/testing/best-of/2025#items","numberOfItems":25,"itemListElement":[{"@type":"ListItem","position":1,"url":"https://daily.dev/posts/the-crash-landing-of-vibe-coding-8crisdutx","name":"The Crash Landing of Vibe Coding"},{"@type":"ListItem","position":2,"url":"https://daily.dev/posts/ep151-24-good-resources-to-learn-software-architecture-in-2025-nrzofimde","name":"EP151: 24 Good Resources to Learn Software Architecture in 2025"},{"@type":"ListItem","position":3,"url":"https://daily.dev/posts/how-to-become-a-confident-software-engineer-0sqq4kapt","name":"How to Become a Confident Software Engineer"},{"@type":"ListItem","position":4,"url":"https://daily.dev/posts/stop-using-typescript-s-exclamation-mark-re1atfub4","name":"Stop Using TypeScript's Exclamation Mark"},{"@type":"ListItem","position":5,"url":"https://daily.dev/posts/before-refactoring-hmjgdgpd5","name":"Before refactoring"},{"@type":"ListItem","position":6,"url":"https://daily.dev/posts/this-is-what-shipping-without-tests-looks-like-c2yvouqfh","name":"This Is What Shipping Without Tests Looks Like"},{"@type":"ListItem","position":7,"url":"https://daily.dev/posts/storybook-9-4zjkvk4qn","name":"Storybook 9"},{"@type":"ListItem","position":8,"url":"https://daily.dev/posts/my-llm-coding-workflow-going-into-2026-vi9oycjke","name":"My LLM coding workflow going into 2026"},{"@type":"ListItem","position":9,"url":"https://daily.dev/posts/dopamine-driven-development-tyla1nofx","name":"Dopamine Driven Development"},{"@type":"ListItem","position":10,"url":"https://daily.dev/posts/postman-is-logging-all-your-secrets-and-environment-variables-0rzc8mjia","name":"Postman is logging all your secrets and environment variables"},{"@type":"ListItem","position":11,"url":"https://daily.dev/posts/applied-software-engineering-at-google--7e87dtdbc","name":"Applied \"Software Engineering at Google\""},{"@type":"ListItem","position":12,"url":"https://daily.dev/posts/write-unit-tests-don-t-waste-our-money--avy3pgrlo","name":"Write Unit Tests, Don't Waste Our Money!"},{"@type":"ListItem","position":13,"url":"https://daily.dev/posts/maestro-aztne232r","name":"Maestro"},{"@type":"ListItem","position":14,"url":"https://daily.dev/posts/unit-test-a-rest-api-everything-you-need-to-know-rk5z44iuw","name":"Unit Test a REST API? Everything You Need to Know"},{"@type":"ListItem","position":15,"url":"https://daily.dev/posts/what-to-look-for-in-code-reviews-i4wijdmsu","name":"What to Look for in Code Reviews"},{"@type":"ListItem","position":16,"url":"https://daily.dev/posts/testing-is-software-engineering-9un4ckzn6","name":"Testing is software engineering"},{"@type":"ListItem","position":17,"url":"https://daily.dev/posts/tdd-is-more-important-than-ever-hoeecbmpk","name":"TDD is more important than ever"},{"@type":"ListItem","position":18,"url":"https://daily.dev/posts/5-best-open-source-tools-for-cross-browser-css-testing-svvgm21bp","name":"5 best open source tools for cross-browser CSS testing"},{"@type":"ListItem","position":19,"url":"https://daily.dev/posts/storybook-10-i8dytibvp","name":"Storybook 10"},{"@type":"ListItem","position":20,"url":"https://daily.dev/posts/your-job-is-to-deliver-code-you-have-proven-to-work-xeabx8mtw","name":"Your job is to deliver code you have proven to work"},{"@type":"ListItem","position":21,"url":"https://daily.dev/posts/unnecessary-anxiety-in-software-development-lko0ht4bi","name":"Unnecessary Anxiety in Software Development"},{"@type":"ListItem","position":22,"url":"https://daily.dev/posts/ai-writes-good-tests-actually-awodep3z3","name":"AI writes good tests, actually"},{"@type":"ListItem","position":23,"url":"https://daily.dev/posts/3-skills-every-early-career-engineer-needs-eqmu12pmd","name":"3 skills every early-career engineer needs"},{"@type":"ListItem","position":24,"url":"https://daily.dev/posts/how-i-use-ai-agents-to-write-code-onvlmqy00","name":"How I use AI agents to write code"},{"@type":"ListItem","position":25,"url":"https://daily.dev/posts/small-repo-high-quality-lzy61mr2i","name":"Small Repo, High Quality"}]},{"@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Tags","item":"https://daily.dev/tags"},{"@type":"ListItem","position":3,"name":"Testing","item":"https://daily.dev/tags/testing"},{"@type":"ListItem","position":4,"name":"Best of","item":"https://daily.dev/tags/testing/best-of"},{"@type":"ListItem","position":5,"name":"2025"}]}]}
```

