{"id":10192,"date":"2026-11-09T06:09:29","date_gmt":"2026-11-09T05:09:29","guid":{"rendered":"https:\/\/www.fratellibertolin.it\/?p=10192"},"modified":"2026-11-09T06:09:43","modified_gmt":"2026-11-09T05:09:43","slug":"software-reliability-check-magicqa20261109-03476","status":"publish","type":"post","link":"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/","title":{"rendered":"Software reliability check MAGICQA20261109 03476"},"content":{"rendered":"


\n<\/span><\/p>\n

\n

Software quality assurance helps teams determine whether an application behaves correctly, remains dependable under expected conditions, and protects data throughout its lifecycle. This technical guide uses MAGICQA20261109 as a temporary publication test label, not as a product name or endorsement. It explains how to plan reliability checks, interpret their results, and connect findings to practical engineering decisions, with quality assurance 03476<\/a> representing a useful reference point for repeatable software testing practices. The focus is on repeatable methods: defining expected behavior, exercising realistic workloads, recording evidence, and addressing risks before they affect users or business operations.<\/p>\n

A practical entry point into software quality assurance<\/h2>\n

Software quality assurance is a planned set of activities that helps prevent defects and evaluate whether software meets its requirements. Reliability checks form an important part of that work. They examine whether an application continues to perform its intended functions over time and in changing conditions, including increased workload, service interruptions, and recovery events. Rather than relying on a single successful test, a sound approach combines repeatable checks with clear acceptance criteria. Teams can then use evidence from development, testing, and production monitoring to understand whether the system is stable enough for its intended use.<\/p>\n

Reliability is not limited to uptime. A service may be available while returning incorrect results, losing updates, or slowing down enough to disrupt essential workflows. Quality assurance therefore considers correctness, resilience, recoverability, and consistency alongside availability. Testers need to understand the system\u2019s critical user journeys, dependencies, data flows, and failure modes before choosing test cases. The MAGICQA20261109 label may identify this publication test in editorial or review records; it does not replace test identifiers, build numbers, environment details, or evidence needed to reproduce an engineering finding.<\/p>\n

How to plan software reliability checks<\/h2>\n

Start by translating requirements into observable outcomes. A useful check has a defined starting state, a repeatable action, an expected result, and a record of what actually happened. The following sequence helps teams create checks that are both technically meaningful and manageable within a software quality assurance process.<\/p>\n

    \n
  1. Identify critical behavior:<\/strong> Select core workflows, important data operations, and dependencies whose failure would materially affect users.<\/li>\n
  2. Set measurable criteria:<\/strong> Define acceptable response times, error rates, recovery targets, and data consistency expectations for each relevant workflow.<\/li>\n
  3. Prepare representative conditions:<\/strong> Use a controlled environment, realistic data, and documented configuration that resembles the intended operating context.<\/li>\n
  4. Run repeatable scenarios:<\/strong> Exercise normal operation, sustained workload, boundary conditions, and selected dependency or service failures.<\/li>\n
  5. Review and record evidence:<\/strong> Compare observations with criteria, preserve logs and environment details, and assign follow-up actions to responsible owners.<\/li>\n<\/ol>\n
      \n
    • Clear criteria make pass and fail decisions more consistent across reviewers.<\/li>\n
    • Representative conditions help reveal issues that isolated component checks may miss.<\/li>\n
    • Preserved evidence makes failures easier to reproduce and investigate.<\/li>\n
    • Assigned follow-up work connects test findings to measurable improvements.<\/li>\n<\/ul>\n

      Practical reliability checks for real software systems<\/h2>\n

      Practical checks should reflect the architecture and risks of the application rather than follow a generic checklist without context. For a service that stores user changes, for example, a reliability scenario can submit an update, interrupt a dependent operation, and then verify whether the system preserves a consistent state after recovery. A performance check can gradually increase concurrent requests while measuring response time, resource use, and error frequency. Teams should repeat important scenarios across relevant builds and record the software version, configuration, test data, and dependencies. This context helps distinguish a product defect from an environmental problem.<\/p>\n

      Reliability testing becomes more useful when failures are designed deliberately and safely. Controlled fault injection can assess whether the application handles a delayed response, unavailable dependency, or temporary network interruption without corrupting data or exposing sensitive information. Recovery checks should verify more than whether a process starts again: they should confirm that queued work is handled appropriately, duplicate actions are controlled, and users receive accurate status. Test environments must be isolated from real customer data and production services unless a separately approved procedure explicitly governs the activity.<\/p>\n

        \n
      • Soak checks:<\/strong> Run a representative workload for an extended period to identify gradual resource growth or intermittent faults.<\/li>\n
      • Load checks:<\/strong> Increase demand in controlled stages and compare response times and error rates with defined thresholds.<\/li>\n
      • Recovery checks:<\/strong> Interrupt a dependency in a test environment, restore it, and confirm that service behavior returns to an acceptable state.<\/li>\n
      • Data integrity checks:<\/strong> Compare expected and observed records after normal operations, retries, and recovery events.<\/li>\n<\/ul>\n

        Results should be interpreted in relation to requirements, not treated as isolated numbers. A response time that is acceptable for a background task may be unsuitable for a user-facing action. Likewise, a low average error rate can hide a serious failure in one critical workflow. Include distributions, outliers, and time-based patterns where possible, then link anomalies to logs, traces, and system metrics. This makes the reliability assessment more informative and helps engineering teams prioritize remediation according to impact and likelihood.<\/p>\n

        Key benefits of a structured reliability assurance process<\/h2>\n

        A structured process gives teams a consistent way to evaluate software behavior before and after changes. It can expose weaknesses earlier, when they are typically easier to investigate, and provide evidence for decisions about release readiness. The value is not simply the number of tests run; it comes from selecting scenarios that address meaningful risks and maintaining checks as the application evolves. Test coverage, reliability indicators, and incident history can be considered together, helping teams understand where assurance is strong and where additional validation is warranted.<\/p>\n

          \n
        • Earlier defect discovery:<\/strong> Repeatable checks can reveal instability before it reaches a wider audience.<\/li>\n
        • More dependable releases:<\/strong> Documented acceptance criteria support informed, evidence-based release decisions.<\/li>\n
        • Faster diagnosis:<\/strong> Versioned test records and diagnostic evidence reduce guesswork during investigation.<\/li>\n
        • Better prioritization:<\/strong> Risk-based scenarios direct effort toward critical workflows and high-impact failure modes.<\/li>\n<\/ul>\n

          These benefits depend on ongoing maintenance. Tests can become misleading when requirements change, environments drift, or test data no longer represents current use. Quality assurance teams should periodically review whether each check still reflects a real risk, whether its thresholds remain justified, and whether failures produce useful diagnostic information. A small, reliable set of high-value checks is often more actionable than a large suite that produces frequent unexplained failures.<\/p>\n

          Trust, security, and reliable test evidence<\/h2>\n

          Reliability checks must protect the confidentiality and integrity of the systems and information they examine. Test data should be synthetic or appropriately anonymized, access to test environments should follow least-privilege principles, and credentials should be managed through approved secure methods. Logs and diagnostic traces can contain sensitive details, so teams should define who may access them, how long they are retained, and how they are disposed of. Fault injection and load generation also need safeguards, including environment boundaries and resource limits, to prevent testing from disrupting unrelated services.<\/p>\n

          Trustworthy evidence is reproducible, traceable, and specific enough to support a conclusion. Record the test objective, relevant requirement, software build, environment configuration, execution time, observed result, and any deviations from the plan. Separate confirmed defects from environmental interruptions or inconclusive outcomes, and avoid claiming that a limited test proves a system will never fail. The temporary label MAGICQA20261109 should be treated only as a publication test marker. It should not be used as evidence of certification, security approval, or a particular reliability result.<\/p>\n

          Choosing a software quality assurance approach for reliability<\/h2>\n

          When selecting a reliability assurance approach, consider how well it connects requirements, test scenarios, evidence, and corrective work. Teams should be able to explain why each check exists, what result is acceptable, and what action follows a failure. A practical approach supports different levels of validation, from focused component tests to end-to-end recovery exercises, while keeping environments controlled and results understandable. It should also accommodate change: as architecture, dependencies, and usage patterns evolve, test coverage and acceptance thresholds must be reviewed rather than assumed to remain valid.<\/p>\n

          Use reliability checks as part of a continuous quality practice, not as a one-time gate. Review trends across builds, investigate recurring failures, and verify that corrective changes address the original risk without creating new problems. The MAGICQA20261109 marker can help identify this article during publication review, while the technical work should remain grounded in requirements, repeatable procedures, and recorded outcomes. With that discipline, software quality assurance can give decision-makers a clearer view of system dependability and help engineering teams improve reliability through measured, verifiable steps.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

          Software quality assurance helps teams determine whether an application behaves correctly, remains dependable under expected conditions, and protects data throughout its lifecycle. This technical guide uses MAGICQA20261109 as a temporary publication test label, not as a product name or endorsement. It explains how to plan reliability checks, interpret their results, and connect findings to practical […]<\/p>\n","protected":false},"author":44,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[70],"tags":[],"class_list":["post-10192","post","type-post","status-publish","format-standard","hentry","category-public"],"yoast_head":"\nSoftware reliability check MAGICQA20261109 03476 - F.lli Bertolin<\/title>\n<meta name=\"description\" content=\"Software quality assurance helps teams determine whether an application behaves correctly, remains dependable under expected conditions, and protects data throughout its lifecycle. This technical guide uses MAGICQA20261109 as a temporary publication test label, not as a product name or endorsement. It explains how to plan reliability checks, interpret their results, and connect findings to practical…\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Software reliability check MAGICQA20261109 03476 - F.lli Bertolin\" \/>\n<meta property=\"og:description\" content=\"Software quality assurance helps teams determine whether an application behaves correctly, remains dependable under expected conditions, and protects data throughout its lifecycle. This technical guide uses MAGICQA20261109 as a temporary publication test label, not as a product name or endorsement. It explains how to plan reliability checks, interpret their results, and connect findings to practical…\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/\" \/>\n<meta property=\"og:site_name\" content=\"F.lli Bertolin\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-09T05:09:29+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-09T05:09:43+00:00\" \/>\n<meta name=\"author\" content=\"wp_service_a63080\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"wp_service_a63080\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/\"},\"author\":{\"name\":\"wp_service_a63080\",\"@id\":\"https:\/\/www.fratellibertolin.it\/#\/schema\/person\/d5cc59a6de5adf399c49d4bdc49f614b\"},\"headline\":\"Software reliability check MAGICQA20261109 03476\",\"datePublished\":\"2026-11-09T05:09:29+00:00\",\"dateModified\":\"2026-11-09T05:09:43+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/\"},\"wordCount\":1384,\"publisher\":{\"@id\":\"https:\/\/www.fratellibertolin.it\/#organization\"},\"articleSection\":[\"public\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.fratellibertolin.it\/en\/en\/software-reliability-check-magicqa20261109-03476\/\",\"url\":\"https:\/\/www.fratellibertolin.it\/en\/en\/software-reliability-check-magicqa20261109-03476\/\",\"name\":\"Software reliability check MAGICQA20261109 03476 - F.lli Bertolin\",\"isPartOf\":{\"@id\":\"https:\/\/www.fratellibertolin.it\/#website\"},\"datePublished\":\"2026-11-09T05:09:29+00:00\",\"dateModified\":\"2026-11-09T05:09:43+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.fratellibertolin.it\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Software reliability check MAGICQA20261109 03476\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.fratellibertolin.it\/en\/#website\",\"url\":\"https:\/\/www.fratellibertolin.it\/en\/\",\"name\":\"F.lli Bertolin\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/www.fratellibertolin.it\/en\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.fratellibertolin.it\/en\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.fratellibertolin.it\/en\/#organization\",\"name\":\"F.lli Bertolin\",\"url\":\"https:\/\/www.fratellibertolin.it\/en\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.fratellibertolin.it\/en\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.fratellibertolin.it\/wp-content\/uploads\/2024\/11\/cropped-favicon.png\",\"contentUrl\":\"https:\/\/www.fratellibertolin.it\/wp-content\/uploads\/2024\/11\/cropped-favicon.png\",\"width\":512,\"height\":512,\"caption\":\"F.lli Bertolin\"},\"image\":{\"@id\":\"https:\/\/www.fratellibertolin.it\/en\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.fratellibertolin.it\/#\/schema\/person\/d5cc59a6de5adf399c49d4bdc49f614b\",\"name\":\"wp_service_a63080\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.fratellibertolin.it\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/0e49041ed91d67b705001bdecf1de74d3d715c3eb87a4c6a8725ba4269acf638?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/0e49041ed91d67b705001bdecf1de74d3d715c3eb87a4c6a8725ba4269acf638?s=96&d=mm&r=g\",\"caption\":\"wp_service_a63080\"},\"url\":\"https:\/\/www.fratellibertolin.it\/en\/author\/wp_service_a63080\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Software reliability check MAGICQA20261109 03476 - F.lli Bertolin","description":"Software quality assurance helps teams determine whether an application behaves correctly, remains dependable under expected conditions, and protects data throughout its lifecycle. This technical guide uses MAGICQA20261109 as a temporary publication test label, not as a product name or endorsement. It explains how to plan reliability checks, interpret their results, and connect findings to practical…","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/","og_locale":"en_US","og_type":"article","og_title":"Software reliability check MAGICQA20261109 03476 - F.lli Bertolin","og_description":"Software quality assurance helps teams determine whether an application behaves correctly, remains dependable under expected conditions, and protects data throughout its lifecycle. This technical guide uses MAGICQA20261109 as a temporary publication test label, not as a product name or endorsement. It explains how to plan reliability checks, interpret their results, and connect findings to practical…","og_url":"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/","og_site_name":"F.lli Bertolin","article_published_time":"2026-11-09T05:09:29+00:00","article_modified_time":"2026-11-09T05:09:43+00:00","author":"wp_service_a63080","twitter_card":"summary_large_image","twitter_misc":{"Written by":"wp_service_a63080","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/#article","isPartOf":{"@id":"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/"},"author":{"name":"wp_service_a63080","@id":"https:\/\/www.fratellibertolin.it\/#\/schema\/person\/d5cc59a6de5adf399c49d4bdc49f614b"},"headline":"Software reliability check MAGICQA20261109 03476","datePublished":"2026-11-09T05:09:29+00:00","dateModified":"2026-11-09T05:09:43+00:00","mainEntityOfPage":{"@id":"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/"},"wordCount":1384,"publisher":{"@id":"https:\/\/www.fratellibertolin.it\/#organization"},"articleSection":["public"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.fratellibertolin.it\/en\/en\/software-reliability-check-magicqa20261109-03476\/","url":"https:\/\/www.fratellibertolin.it\/en\/en\/software-reliability-check-magicqa20261109-03476\/","name":"Software reliability check MAGICQA20261109 03476 - F.lli Bertolin","isPartOf":{"@id":"https:\/\/www.fratellibertolin.it\/#website"},"datePublished":"2026-11-09T05:09:29+00:00","dateModified":"2026-11-09T05:09:43+00:00","breadcrumb":{"@id":"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.fratellibertolin.it\/en\/software-reliability-check-magicqa20261109-03476\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.fratellibertolin.it\/"},{"@type":"ListItem","position":2,"name":"Software reliability check MAGICQA20261109 03476"}]},{"@type":"WebSite","@id":"https:\/\/www.fratellibertolin.it\/en\/#website","url":"https:\/\/www.fratellibertolin.it\/en\/","name":"F.lli Bertolin","description":"","publisher":{"@id":"https:\/\/www.fratellibertolin.it\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.fratellibertolin.it\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.fratellibertolin.it\/en\/#organization","name":"F.lli Bertolin","url":"https:\/\/www.fratellibertolin.it\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.fratellibertolin.it\/en\/#\/schema\/logo\/image\/","url":"https:\/\/www.fratellibertolin.it\/wp-content\/uploads\/2024\/11\/cropped-favicon.png","contentUrl":"https:\/\/www.fratellibertolin.it\/wp-content\/uploads\/2024\/11\/cropped-favicon.png","width":512,"height":512,"caption":"F.lli Bertolin"},"image":{"@id":"https:\/\/www.fratellibertolin.it\/en\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.fratellibertolin.it\/#\/schema\/person\/d5cc59a6de5adf399c49d4bdc49f614b","name":"wp_service_a63080","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.fratellibertolin.it\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/0e49041ed91d67b705001bdecf1de74d3d715c3eb87a4c6a8725ba4269acf638?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/0e49041ed91d67b705001bdecf1de74d3d715c3eb87a4c6a8725ba4269acf638?s=96&d=mm&r=g","caption":"wp_service_a63080"},"url":"https:\/\/www.fratellibertolin.it\/en\/author\/wp_service_a63080\/"}]}},"_links":{"self":[{"href":"https:\/\/www.fratellibertolin.it\/en\/wp-json\/wp\/v2\/posts\/10192","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fratellibertolin.it\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fratellibertolin.it\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fratellibertolin.it\/en\/wp-json\/wp\/v2\/users\/44"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fratellibertolin.it\/en\/wp-json\/wp\/v2\/comments?post=10192"}],"version-history":[{"count":1,"href":"https:\/\/www.fratellibertolin.it\/en\/wp-json\/wp\/v2\/posts\/10192\/revisions"}],"predecessor-version":[{"id":10193,"href":"https:\/\/www.fratellibertolin.it\/en\/wp-json\/wp\/v2\/posts\/10192\/revisions\/10193"}],"wp:attachment":[{"href":"https:\/\/www.fratellibertolin.it\/en\/wp-json\/wp\/v2\/media?parent=10192"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fratellibertolin.it\/en\/wp-json\/wp\/v2\/categories?post=10192"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fratellibertolin.it\/en\/wp-json\/wp\/v2\/tags?post=10192"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}