{"id":3689,"date":"2026-11-09T06:06:47","date_gmt":"2026-11-09T05:06:47","guid":{"rendered":"https:\/\/caencharpente.fr\/?p=3689"},"modified":"2026-11-09T06:06:58","modified_gmt":"2026-11-09T05:06:58","slug":"software-reliability-check-magicqa20261109-02460","status":"publish","type":"post","link":"https:\/\/caencharpente.fr\/?p=3689","title":{"rendered":"Software reliability check MAGICQA20261109 02460"},"content":{"rendered":"<p><!--zk:idk=pub1-81520540-169f-5d7e-95dc-100296249d73--><br \/>\n<span class=\"zk-idempotency-marker\" data-zk-idk=\"pub1-81520540-169f-5d7e-95dc-100296249d73\" style=\"display:none\"><\/span><\/p>\n<div class=\"zk-article\">\n<p>Software reliability checks help teams determine whether an application continues to behave correctly under expected conditions and foreseeable stress. This technical article uses MAGICQA20261109 as a temporary publication test label, not as a product or certification. It explains how quality assurance teams can define reliability goals, design repeatable checks, interpret failures, and use evidence to guide release decisions, with <a href=\"https:\/\/example.net\/\">quality assurance 02460<\/a> practices supporting consistent software testing across teams. The focus is on practical software testing methods, including availability, recovery, fault tolerance, and performance over time.<\/p>\n<h2>What matters when assessing software reliability<\/h2>\n<p>Reliability describes the ability of software to perform its required functions consistently for a stated period and under defined operating conditions. A useful assessment begins with clear expectations: which user journeys must work, what level of service is acceptable, and how quickly the system should recover from failure. Without those definitions, a test may produce many measurements but little decision-making value. Quality assurance teams should connect reliability checks to service requirements, such as successful transaction completion, accurate data handling, and predictable responses when dependencies are slow or unavailable.<\/p>\n<p>MAGICQA20261109 is included solely to identify this temporary publication test. The label does not imply that any particular system has passed an assessment. A credible reliability review depends on traceable test conditions, representative environments, and evidence that can be repeated. Teams should consider normal usage as well as less common situations, including traffic peaks, interrupted connections, expired credentials, resource limits, and recovery after a process restart. Documenting these conditions makes results easier to compare across builds and helps distinguish a genuine reliability improvement from a change in test setup.<\/p>\n<h2>How to organize a software reliability check<\/h2>\n<p>Start with a narrow, measurable objective and then expand coverage according to system risk. A check should identify the component or workflow under review, the conditions it will face, the signals that indicate success, and the evidence required for a release decision. The following sequence offers a repeatable foundation for planning reliability work across development and quality assurance teams.<\/p>\n<ol>\n<li><strong>Define the reliability objective:<\/strong> Specify the required behavior, operating period, workload, and acceptable failure rate for the feature or service being tested.<\/li>\n<li><strong>Map critical dependencies:<\/strong> Record the databases, network services, queues, and external interfaces that could affect the workflow.<\/li>\n<li><strong>Prepare a representative environment:<\/strong> Match relevant configuration and data characteristics while keeping test conditions controlled and documented.<\/li>\n<li><strong>Run normal and failure scenarios:<\/strong> Exercise expected usage, then introduce controlled interruptions, delays, restarts, or resource pressure.<\/li>\n<li><strong>Review evidence and decide:<\/strong> Compare results with agreed thresholds, investigate anomalies, and record follow-up actions before release.<\/li>\n<\/ol>\n<ul>\n<li>Objectives tied to measurable user and system outcomes.<\/li>\n<li>Dependencies made visible before failures occur.<\/li>\n<li>Repeatable scenarios that support build-to-build comparison.<\/li>\n<li>Recorded evidence to clarify quality decisions.<\/li>\n<\/ul>\n<h2>Practical reliability checks in the test environment<\/h2>\n<p>Practical checks should combine functional assertions with operational measurements. For example, a team can repeatedly submit a representative request while monitoring response time, error rate, resource use, and data consistency. The test should verify not only that the application returns a response, but also that the response is correct and that repeated activity does not create duplicate records or lose updates. When the system relies on a database or service interface, controlled latency and temporary unavailability can reveal whether timeouts, retries, and fallback behavior are safe. Every injected fault should be bounded, documented, and reversible.<\/p>\n<p>Long-running checks are useful when defects emerge only after sustained activity, such as memory growth, connection exhaustion, or gradual degradation in response time. Stress and load testing answer different questions: load testing evaluates behavior under expected demand, while stress testing explores limits and recovery beyond ordinary conditions. Teams should avoid treating a single successful run as proof of reliability. Repetition, varied input, stable monitoring, and comparison against a baseline improve confidence. The test record should include build identification, environment configuration, workload profile, start and end times, observed incidents, and any limitations that could affect interpretation.<\/p>\n<ul>\n<li><strong>Availability:<\/strong> Measure whether critical functions remain accessible during the defined test window.<\/li>\n<li><strong>Recovery:<\/strong> Confirm that service resumes correctly after a controlled restart or dependency interruption.<\/li>\n<li><strong>Data integrity:<\/strong> Check that saved records remain accurate and consistent after retries or failures.<\/li>\n<li><strong>Performance stability:<\/strong> Track response times and resource consumption during sustained representative use.<\/li>\n<\/ul>\n<p>These checks become more valuable when linked to the application\u2019s risk profile. A low-impact display defect may need a different threshold from a failure that prevents users from completing a critical workflow. Teams can prioritize scenarios by estimating the likelihood of failure, the severity of its effect, and the difficulty of detecting it in production. This approach keeps testing focused while still encouraging broad coverage of important failure modes. Findings should identify both the observed symptom and its likely cause, so engineers can address system weaknesses rather than merely suppressing a failing test.<\/p>\n<h2>Benefits of evidence-based reliability testing<\/h2>\n<p>A structured reliability program gives teams a clearer view of software behavior than ad hoc checks alone. It creates a shared basis for discussing acceptable risk, supports more informed release decisions, and helps direct engineering effort toward issues with meaningful user or operational impact. The value does not come from producing the largest possible number of test runs. It comes from selecting scenarios that reflect real requirements, collecting trustworthy measurements, and following defects through resolution. MAGICQA20261109 remains only a temporary label; the durable benefit is a documented process that can be repeated and improved.<\/p>\n<ul>\n<li><strong>Earlier defect discovery:<\/strong> Controlled fault scenarios can expose fragile recovery behavior before deployment.<\/li>\n<li><strong>More useful release evidence:<\/strong> Measured results make readiness reviews less dependent on intuition.<\/li>\n<li><strong>Improved regression coverage:<\/strong> Saved scenarios help detect when later changes weaken previously stable behavior.<\/li>\n<li><strong>Better operational preparation:<\/strong> Observed failure patterns can inform monitoring and incident response plans.<\/li>\n<\/ul>\n<p>Reliability results also support continuous improvement when teams treat them as feedback rather than a one-time gate. A recurring timeout may indicate an unsuitable limit, an overloaded dependency, or a missing recovery path. Comparing results across builds can reveal whether a fix improved the target behavior without creating new problems elsewhere. Findings should be prioritized, assigned, and retested with the original conditions whenever possible. This disciplined cycle strengthens both software quality assurance and the shared understanding of how the application behaves under pressure.<\/p>\n<h2>Trustworthy methods for reliability and security<\/h2>\n<p>Trust in a reliability result depends on test integrity. Use controlled accounts and data, limit access to test environments, and avoid exposing private information in logs or reports. Fault injection should be performed only in an authorized environment with safeguards that prevent disruption to production services. Test tools and configuration should be versioned or otherwise recorded, so another reviewer can understand how the result was produced. If monitoring data is incomplete, the report should state that limitation rather than presenting uncertain conclusions as proof. Clear records help reviewers assess whether a result is relevant, reproducible, and sufficiently representative.<\/p>\n<p>Security and reliability often intersect. A service that handles invalid input safely, protects session state during interruptions, and recovers without exposing sensitive data is more dependable as well as more secure. Quality assurance teams should include relevant access-control and data-protection expectations in failure scenarios, while coordinating with security specialists for higher-risk testing. Reports should distinguish verified observations from assumptions and include enough detail to reproduce issues without revealing secrets. The temporary publication label MAGICQA20261109 does not certify software, validate a test environment, or replace independent review; it simply identifies this article\u2019s publication test.<\/p>\n<h2>Choosing a useful reliability approach for your software<\/h2>\n<p>The right reliability approach is the one that reflects the system\u2019s intended use, risks, and operating constraints. Before accepting a test plan, check that each scenario has a clear purpose, a measurable outcome, and a safe way to run it. Confirm that results include environment details and that failure thresholds were agreed in advance. A plan should cover ordinary workflows, important dependencies, and credible disruptions, while remaining practical enough to repeat after meaningful code changes. These criteria help teams avoid both superficial checks and unnecessarily broad testing that produces evidence without clear decisions.<\/p>\n<p>For software quality assurance, reliability is an ongoing property to evaluate, not a permanent status granted by one successful test. Teams should review scenarios as architecture, usage patterns, and service expectations change. Preserve useful baselines, investigate unexpected variation, and verify fixes under conditions that reproduce the original failure. When reporting conclusions, explain what was tested, what was not tested, and how the findings affect release risk. That transparent approach makes MAGICQA20261109 an appropriate temporary label for this publication while keeping attention on the central task: assessing software behavior with careful, repeatable evidence.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Software reliability checks help teams determine whether an application continues to behave correctly under expected conditions and foreseeable stress. This technical article uses MAGICQA20261109 as a temporary publication test label, not as a product or certification. It explains how quality assurance teams can define reliability goals, design repeatable checks, interpret failures, and use evidence to [&hellip;]<\/p>\n","protected":false},"author":54,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ocean_post_layout":"","ocean_both_sidebars_style":"","ocean_both_sidebars_content_width":0,"ocean_both_sidebars_sidebars_width":0,"ocean_sidebar":"","ocean_second_sidebar":"","ocean_disable_margins":"enable","ocean_add_body_class":"","ocean_shortcode_before_top_bar":"","ocean_shortcode_after_top_bar":"","ocean_shortcode_before_header":"","ocean_shortcode_after_header":"","ocean_has_shortcode":"","ocean_shortcode_after_title":"","ocean_shortcode_before_footer_widgets":"","ocean_shortcode_after_footer_widgets":"","ocean_shortcode_before_footer_bottom":"","ocean_shortcode_after_footer_bottom":"","ocean_display_top_bar":"default","ocean_display_header":"default","ocean_header_style":"","ocean_center_header_left_menu":"","ocean_custom_header_template":"","ocean_custom_logo":0,"ocean_custom_retina_logo":0,"ocean_custom_logo_max_width":0,"ocean_custom_logo_tablet_max_width":0,"ocean_custom_logo_mobile_max_width":0,"ocean_custom_logo_max_height":0,"ocean_custom_logo_tablet_max_height":0,"ocean_custom_logo_mobile_max_height":0,"ocean_header_custom_menu":"","ocean_menu_typo_font_family":"","ocean_menu_typo_font_subset":"","ocean_menu_typo_font_size":0,"ocean_menu_typo_font_size_tablet":0,"ocean_menu_typo_font_size_mobile":0,"ocean_menu_typo_font_size_unit":"px","ocean_menu_typo_font_weight":"","ocean_menu_typo_font_weight_tablet":"","ocean_menu_typo_font_weight_mobile":"","ocean_menu_typo_transform":"","ocean_menu_typo_transform_tablet":"","ocean_menu_typo_transform_mobile":"","ocean_menu_typo_line_height":0,"ocean_menu_typo_line_height_tablet":0,"ocean_menu_typo_line_height_mobile":0,"ocean_menu_typo_line_height_unit":"","ocean_menu_typo_spacing":0,"ocean_menu_typo_spacing_tablet":0,"ocean_menu_typo_spacing_mobile":0,"ocean_menu_typo_spacing_unit":"","ocean_menu_link_color":"","ocean_menu_link_color_hover":"","ocean_menu_link_color_active":"","ocean_menu_link_background":"","ocean_menu_link_hover_background":"","ocean_menu_link_active_background":"","ocean_menu_social_links_bg":"","ocean_menu_social_hover_links_bg":"","ocean_menu_social_links_color":"","ocean_menu_social_hover_links_color":"","ocean_disable_title":"default","ocean_disable_heading":"default","ocean_post_title":"","ocean_post_subheading":"","ocean_post_title_style":"","ocean_post_title_background_color":"","ocean_post_title_background":0,"ocean_post_title_bg_image_position":"","ocean_post_title_bg_image_attachment":"","ocean_post_title_bg_image_repeat":"","ocean_post_title_bg_image_size":"","ocean_post_title_height":0,"ocean_post_title_bg_overlay":0.5,"ocean_post_title_bg_overlay_color":"","ocean_disable_breadcrumbs":"default","ocean_breadcrumbs_color":"","ocean_breadcrumbs_separator_color":"","ocean_breadcrumbs_links_color":"","ocean_breadcrumbs_links_hover_color":"","ocean_display_footer_widgets":"default","ocean_display_footer_bottom":"default","ocean_custom_footer_template":"","ocean_post_oembed":"","ocean_post_self_hosted_media":"","ocean_post_video_embed":"","ocean_link_format":"","ocean_link_format_target":"self","ocean_quote_format":"","ocean_quote_format_link":"post","ocean_gallery_link_images":"on","ocean_gallery_id":[],"footnotes":""},"categories":[7],"tags":[],"class_list":["post-3689","post","type-post","status-publish","format-standard","hentry","category-public","entry"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.0 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Software reliability check MAGICQA20261109 02460 - Caen Charpente<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/caencharpente.fr\/?p=3689\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Software reliability check MAGICQA20261109 02460 - Caen Charpente\" \/>\n<meta property=\"og:description\" content=\"Software reliability checks help teams determine whether an application continues to behave correctly under expected conditions and foreseeable stress. This technical article uses MAGICQA20261109 as a temporary publication test label, not as a product or certification. It explains how quality assurance teams can define reliability goals, design repeatable checks, interpret failures, and use evidence to [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/caencharpente.fr\/?p=3689\" \/>\n<meta property=\"og:site_name\" content=\"Caen Charpente\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-09T05:06:47+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-09T05:06:58+00:00\" \/>\n<meta name=\"author\" content=\"yun_11\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"yun_11\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\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:\/\/caencharpente.fr\/?p=3689#article\",\"isPartOf\":{\"@id\":\"https:\/\/caencharpente.fr\/?p=3689\"},\"author\":{\"name\":\"yun_11\",\"@id\":\"https:\/\/caencharpente.fr\/#\/schema\/person\/d1307ab0592259d0f5c2e96b3f02f28f\"},\"headline\":\"Software reliability check MAGICQA20261109 02460\",\"datePublished\":\"2026-11-09T05:06:47+00:00\",\"dateModified\":\"2026-11-09T05:06:58+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/caencharpente.fr\/?p=3689\"},\"wordCount\":1423,\"publisher\":{\"@id\":\"https:\/\/caencharpente.fr\/#organization\"},\"articleSection\":[\"public\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/caencharpente.fr\/?p=3689\",\"url\":\"https:\/\/caencharpente.fr\/?p=3689\",\"name\":\"Software reliability check MAGICQA20261109 02460 - Caen Charpente\",\"isPartOf\":{\"@id\":\"https:\/\/caencharpente.fr\/#website\"},\"datePublished\":\"2026-11-09T05:06:47+00:00\",\"dateModified\":\"2026-11-09T05:06:58+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/caencharpente.fr\/?p=3689#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/caencharpente.fr\/?p=3689\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/caencharpente.fr\/?p=3689#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/caencharpente.fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Software reliability check MAGICQA20261109 02460\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/caencharpente.fr\/#website\",\"url\":\"https:\/\/caencharpente.fr\/\",\"name\":\"Caen Charpente\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/caencharpente.fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/caencharpente.fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/caencharpente.fr\/#organization\",\"name\":\"Caen Charpente\",\"url\":\"https:\/\/caencharpente.fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/caencharpente.fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/caencharpente.fr\/wp-content\/uploads\/2023\/08\/cropped-cropped-cropped-Logo_CharpMenui_RVB__2_-removebg-preview-1920w.webp\",\"contentUrl\":\"https:\/\/caencharpente.fr\/wp-content\/uploads\/2023\/08\/cropped-cropped-cropped-Logo_CharpMenui_RVB__2_-removebg-preview-1920w.webp\",\"width\":1006,\"height\":248,\"caption\":\"Caen Charpente\"},\"image\":{\"@id\":\"https:\/\/caencharpente.fr\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/caencharpente.fr\/#\/schema\/person\/d1307ab0592259d0f5c2e96b3f02f28f\",\"name\":\"yun_11\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/caencharpente.fr\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/79268721c0d90d6de4e391efc50a44540b9e474fb11b1fc995d7dbdbc43d7fb6?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/79268721c0d90d6de4e391efc50a44540b9e474fb11b1fc995d7dbdbc43d7fb6?s=96&d=mm&r=g\",\"caption\":\"yun_11\"},\"url\":\"https:\/\/caencharpente.fr\/?author=54\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Software reliability check MAGICQA20261109 02460 - Caen Charpente","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:\/\/caencharpente.fr\/?p=3689","og_locale":"fr_FR","og_type":"article","og_title":"Software reliability check MAGICQA20261109 02460 - Caen Charpente","og_description":"Software reliability checks help teams determine whether an application continues to behave correctly under expected conditions and foreseeable stress. This technical article uses MAGICQA20261109 as a temporary publication test label, not as a product or certification. It explains how quality assurance teams can define reliability goals, design repeatable checks, interpret failures, and use evidence to [&hellip;]","og_url":"https:\/\/caencharpente.fr\/?p=3689","og_site_name":"Caen Charpente","article_published_time":"2026-11-09T05:06:47+00:00","article_modified_time":"2026-11-09T05:06:58+00:00","author":"yun_11","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"yun_11","Dur\u00e9e de lecture estim\u00e9e":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/caencharpente.fr\/?p=3689#article","isPartOf":{"@id":"https:\/\/caencharpente.fr\/?p=3689"},"author":{"name":"yun_11","@id":"https:\/\/caencharpente.fr\/#\/schema\/person\/d1307ab0592259d0f5c2e96b3f02f28f"},"headline":"Software reliability check MAGICQA20261109 02460","datePublished":"2026-11-09T05:06:47+00:00","dateModified":"2026-11-09T05:06:58+00:00","mainEntityOfPage":{"@id":"https:\/\/caencharpente.fr\/?p=3689"},"wordCount":1423,"publisher":{"@id":"https:\/\/caencharpente.fr\/#organization"},"articleSection":["public"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/caencharpente.fr\/?p=3689","url":"https:\/\/caencharpente.fr\/?p=3689","name":"Software reliability check MAGICQA20261109 02460 - Caen Charpente","isPartOf":{"@id":"https:\/\/caencharpente.fr\/#website"},"datePublished":"2026-11-09T05:06:47+00:00","dateModified":"2026-11-09T05:06:58+00:00","breadcrumb":{"@id":"https:\/\/caencharpente.fr\/?p=3689#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/caencharpente.fr\/?p=3689"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/caencharpente.fr\/?p=3689#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/caencharpente.fr\/"},{"@type":"ListItem","position":2,"name":"Software reliability check MAGICQA20261109 02460"}]},{"@type":"WebSite","@id":"https:\/\/caencharpente.fr\/#website","url":"https:\/\/caencharpente.fr\/","name":"Caen Charpente","description":"","publisher":{"@id":"https:\/\/caencharpente.fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/caencharpente.fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/caencharpente.fr\/#organization","name":"Caen Charpente","url":"https:\/\/caencharpente.fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/caencharpente.fr\/#\/schema\/logo\/image\/","url":"https:\/\/caencharpente.fr\/wp-content\/uploads\/2023\/08\/cropped-cropped-cropped-Logo_CharpMenui_RVB__2_-removebg-preview-1920w.webp","contentUrl":"https:\/\/caencharpente.fr\/wp-content\/uploads\/2023\/08\/cropped-cropped-cropped-Logo_CharpMenui_RVB__2_-removebg-preview-1920w.webp","width":1006,"height":248,"caption":"Caen Charpente"},"image":{"@id":"https:\/\/caencharpente.fr\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/caencharpente.fr\/#\/schema\/person\/d1307ab0592259d0f5c2e96b3f02f28f","name":"yun_11","image":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/caencharpente.fr\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/79268721c0d90d6de4e391efc50a44540b9e474fb11b1fc995d7dbdbc43d7fb6?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/79268721c0d90d6de4e391efc50a44540b9e474fb11b1fc995d7dbdbc43d7fb6?s=96&d=mm&r=g","caption":"yun_11"},"url":"https:\/\/caencharpente.fr\/?author=54"}]}},"_links":{"self":[{"href":"https:\/\/caencharpente.fr\/index.php?rest_route=\/wp\/v2\/posts\/3689","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/caencharpente.fr\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/caencharpente.fr\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/caencharpente.fr\/index.php?rest_route=\/wp\/v2\/users\/54"}],"replies":[{"embeddable":true,"href":"https:\/\/caencharpente.fr\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3689"}],"version-history":[{"count":1,"href":"https:\/\/caencharpente.fr\/index.php?rest_route=\/wp\/v2\/posts\/3689\/revisions"}],"predecessor-version":[{"id":3690,"href":"https:\/\/caencharpente.fr\/index.php?rest_route=\/wp\/v2\/posts\/3689\/revisions\/3690"}],"wp:attachment":[{"href":"https:\/\/caencharpente.fr\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3689"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/caencharpente.fr\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3689"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/caencharpente.fr\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3689"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}