{"id":1119,"date":"2026-02-25T10:36:03","date_gmt":"2026-02-25T10:36:03","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/"},"modified":"2026-03-02T09:14:03","modified_gmt":"2026-03-02T09:14:03","slug":"user-story-testing-agile","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/","title":{"rendered":"Integrating User Stories with Testing and QA"},"content":{"rendered":"<p>A customer service team logs a story: \u201cAs a support agent, I want to filter tickets by priority so I can respond to urgent issues first.\u201d The team agrees it\u2019s clear and valuable. But when the developer implements it, the filter doesn\u2019t work as expected. The product owner is surprised. The QA engineer discovers the issue: no test case covered the logic for \u201curgent\u201d vs. \u201chigh\u201d priority.<\/p>\n<p>That\u2019s the hidden cost of skipping user story testing. A story can look perfect on paper but fail in delivery if the acceptance criteria aren\u2019t built to be testable. I\u2019ve seen teams lose weeks on rework because they treated acceptance criteria as documentation, not as the foundation for test design.<\/p>\n<p>This chapter shows how to transform user stories into testable units through structured acceptance criteria. You\u2019ll learn how QA isn\u2019t just a gatekeeper but a key collaborator in refining stories. You\u2019ll also see how acceptance test agile practices ensure that every story is not just built, but validated.<\/p>\n<p>By the end, you\u2019ll know how to make your stories testable from day one\u2014reducing rework, speeding up feedback, and building confidence across the team.<\/p>\n<h2>Why Acceptance Criteria Are the Backbone of Testable Stories<\/h2>\n<p>Acceptance criteria are not optional. They are the bridge between a story\u2019s intent and its validation. Without them, teams rely on assumptions. With them, there\u2019s clarity.<\/p>\n<p>My first experience with poorly defined criteria taught me this: a story about \u201cimproving login speed\u201d with no measurable outcome led to endless debates. It wasn\u2019t until we added: \u201cThe login page should load in under 1.5 seconds under 1000 concurrent users\u201d that we knew when it was done.<\/p>\n<p>Good acceptance criteria must be specific, measurable, and unambiguous. They should reflect real user behavior, not technical features.<\/p>\n<h3>What Makes a Good Acceptance Criterion?<\/h3>\n<p>Start with the INVEST principles, but apply them through a testing lens. A testable story must be:<\/p>\n<ul>\n<li><strong>Independent:<\/strong> Criteria should not depend on other stories to be testable.<\/li>\n<li><strong>Testable:<\/strong> Each criterion must be verifiable through a test case or automated check.<\/li>\n<li><strong>Small:<\/strong> If a story is too big, acceptance criteria become unwieldy. Split early.<\/li>\n<li><strong>Verifiable:<\/strong> A test must be able to pass or fail\u2014no vague terms like \u201cfast\u201d or \u201cnice.\u201d<\/li>\n<\/ul>\n<p>Testability isn\u2019t just about automation. It\u2019s about clarity. When a QA engineer can write a test from your criteria, the story is ready.<\/p>\n<h2>How QA Teams Turn Stories into Test Cases<\/h2>\n<p>QA doesn\u2019t wait for the code. They co-create test cases during refinement. This is where acceptance test agile practices become tangible.<\/p>\n<p>When I worked on a fintech product, we used a simple rule: every story must have at least one testable acceptance criterion per business rule. For a story like \u201cAs a customer, I want to transfer money between accounts so I can manage my funds,\u201d we defined:<\/p>\n<ul>\n<li>Given I\u2019m logged in, when I select the transfer option, then I should see a list of my linked accounts.<\/li>\n<li>Given I select two accounts, when I enter an amount less than my balance, then the transfer should be processed.<\/li>\n<li>Given I enter an amount greater than my balance, when I confirm, then I should see an \u201cInsufficient funds\u201d error.<\/li>\n<\/ul>\n<p>These aren\u2019t just conditions\u2014they\u2019re testable scenarios. The QA team used them to write both manual and automated test cases, and the results were immediate: no surprises in testing, no last-minute bug fixes.<\/p>\n<h3>Creating Test Cases from Acceptance Criteria<\/h3>\n<p>Use a standardized format to turn criteria into test cases:<\/p>\n<ol>\n<li>Write the story in \u201cAs a&#8230; I want&#8230; so that&#8230;\u201d format.<\/li>\n<li>For each acceptance criterion, draft a \u201cGiven-When-Then\u201d scenario.<\/li>\n<li>Assign test ownership (QA, dev, or both).<\/li>\n<li>Map to a test case ID in your test management tool.<\/li>\n<\/ol>\n<p>This process ensures alignment and traceability. It also makes it easy to update tests when the story evolves.<\/p>\n<h2>Collaborating on Acceptance Test Agile Workflows<\/h2>\n<p>Acceptance test agile isn\u2019t a one-off. It\u2019s a continuous loop between product, development, and QA. The key is timing.<\/p>\n<p>Here\u2019s how we ran it: during backlog refinement, the QA engineer attended the session and asked, \u201cHow would you verify this?\u201d Their question forced the team to write testable criteria. In one sprint, a story about \u201cemail notifications\u201d was initially vague. The QA asked: \u201cWhat triggers the email? Who receives it? What does it include?\u201d That led to three crisp acceptance criteria and a clear test plan.<\/p>\n<p>Teams that integrate QA early see 40% fewer bugs in production. The cost of catching a bug in post-release testing is 15 times higher than in design.<\/p>\n<h3>QA User Stories: A Collaborative Framework<\/h3>\n<p>QA doesn\u2019t just test stories\u2014they help write them. When a QA engineer says, \u201cWhat happens if the user cancels during checkout?\u201d they\u2019re not being disruptive. They\u2019re uncovering a missing scenario.<\/p>\n<p>Use this checklist during story refinement:<\/p>\n<ul>\n<li>Is there a testable scenario for success?<\/li>\n<li>Are edge cases covered (e.g., invalid input, timeout, network failure)?<\/li>\n<li>Can the test be automated? If not, why not?<\/li>\n<li>Is the testable outcome aligned with business value?<\/li>\n<\/ul>\n<p>When these are addressed, the story is not just testable\u2014it\u2019s robust.<\/p>\n<h2>Practical Example: Testing a Payment Processing Story<\/h2>\n<p>Consider this story:<\/p>\n<p><em>As a shopper, I want to pay with a credit card so that I can complete my purchase quickly.<\/em><\/p>\n<p>Here\u2019s how we turned it into testable criteria:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Acceptance Criterion<\/th>\n<th>Test Type<\/th>\n<th>Expected Outcome<\/th>\n<\/tr>\n<tr>\n<td>Given a valid credit card number, when I enter it and submit, then the system should confirm payment processing.<\/td>\n<td>Automated (UI)<\/td>\n<td>Success message appears<\/td>\n<\/tr>\n<tr>\n<td>Given an invalid card number, when I submit, then the system should show an error.<\/td>\n<td>Automated (API)<\/td>\n<td>Validation error returned<\/td>\n<\/tr>\n<tr>\n<td>Given the card is expired, when I submit, then the system should reject the transaction.<\/td>\n<td>Manual (QA)<\/td>\n<td>\u201cCard expired\u201d message displayed<\/td>\n<\/tr>\n<tr>\n<td>Given a declined transaction, when I retry, then I should see a fallback option to contact support.<\/td>\n<td>Manual (UX)<\/td>\n<td>Support contact link appears<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The QA team labeled each test with a status (to-be-tested, passed, failed), linked it to the story ID, and updated the sprint dashboard in real time.<\/p>\n<p>This approach didn\u2019t just prevent bugs\u2014it built trust. Stakeholders could see exactly what was tested and what worked.<\/p>\n<h2>Common Pitfalls in User Story Testing<\/h2>\n<p>Even well-intentioned teams fall into traps. Here are the top three:<\/p>\n<ol>\n<li><strong>Vague criteria:<\/strong> \u201cThe system should work fast.\u201d This can\u2019t be tested. Replace with \u201cThe checkout process should complete in under 3 seconds.\u201d<\/li>\n<li><strong>Too many criteria:<\/strong> More than 5 acceptance criteria per story increases cognitive load and reduces test coverage quality.<\/li>\n<li><strong>Missing negative scenarios:<\/strong> Teams focus on \u201chappy path\u201d only. QA must ask: \u201cWhat if the user enters invalid data?\u201d<\/li>\n<\/ol>\n<p>These mistakes aren\u2019t just about poor writing\u2014they\u2019re about missing the core of acceptance test agile: validation through variation, not just success.<\/p>\n<h2>Best Practices for Integration<\/h2>\n<p>Build user story testing into your Agile workflow:<\/p>\n<ul>\n<li>Hold a 10-minute QA review during story refinement.<\/li>\n<li>Use a shared acceptance criteria template with fields: Condition, Action, Result.<\/li>\n<li>Link each test case to the story in your backlog tool.<\/li>\n<li>Update test status in sprint demos\u2014show what passed, what failed, and why.<\/li>\n<li>Review failed tests in retrospectives: Why did the story fail? Was the acceptance criterion incomplete?<\/li>\n<\/ul>\n<p>This turns testing into a feedback loop\u2014not a gate.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do acceptance criteria relate to test cases?<\/h3>\n<p>Each acceptance criterion should map to at least one test case. The criterion defines the scenario, and the test case defines the steps and expected outcome. This ensures traceability and accountability.<\/p>\n<h3>Can QA write acceptance criteria?<\/h3>\n<p>Yes\u2014and they should. QA brings a user-centric, risk-aware perspective. Their input improves scenario coverage and test quality. Collaboration is essential.<\/p>\n<h3>Do I need to write test cases for every story?<\/h3>\n<p>Yes, if the story has any functional logic. Even small stories (e.g., \u201cchange button color\u201d) need a test to verify the visual change. If it can\u2019t be tested, it\u2019s not ready.<\/p>\n<h3>Why is user story testing important in Agile?<\/h3>\n<p>It ensures every story delivers verifiable value. It reduces rework, prevents scope creep, and builds trust between teams and stakeholders. It\u2019s the foundation of continuous delivery.<\/p>\n<h3>How do I handle untestable stories?<\/h3>\n<p>Revisit the acceptance criteria. Ask: \u201cCan this be verified?\u201d If not, split the story or rephrase it. If it\u2019s purely UX, use visual testing or user feedback instead. Always aim for testable outcomes.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A customer service team logs a story: \u201cAs a support agent, I want to filter tickets by priority so I can respo [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1115,"menu_order":3,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-1119","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>User Story Testing: From Stories to Testable Outcomes<\/title>\n<meta name=\"description\" content=\"Master user story testing with real-world techniques. Learn how acceptance criteria fuel agile testing and how QA teams collaborate to ensure every story delivers value and quality.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"User Story Testing: From Stories to Testable Outcomes\" \/>\n<meta property=\"og:description\" content=\"Master user story testing with real-world techniques. Learn how acceptance criteria fuel agile testing and how QA teams collaborate to ensure every story delivers value and quality.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills\u65e5\u672c\u8a9e\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:14:03+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"7\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/\",\"name\":\"User Story Testing: From Stories to Testable Outcomes\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-02-25T10:36:03+00:00\",\"dateModified\":\"2026-03-02T09:14:03+00:00\",\"description\":\"Master user story testing with real-world techniques. Learn how acceptance criteria fuel agile testing and how QA teams collaborate to ensure every story delivers value and quality.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Write Effective User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"From Story to Delivery\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Integrating User Stories with Testing and QA\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"User Story Testing: From Stories to Testable Outcomes","description":"Master user story testing with real-world techniques. Learn how acceptance criteria fuel agile testing and how QA teams collaborate to ensure every story delivers value and quality.","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:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/","og_locale":"ja_JP","og_type":"article","og_title":"User Story Testing: From Stories to Testable Outcomes","og_description":"Master user story testing with real-world techniques. Learn how acceptance criteria fuel agile testing and how QA teams collaborate to ensure every story delivers value and quality.","og_url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/","og_site_name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","article_modified_time":"2026-03-02T09:14:03+00:00","twitter_card":"summary_large_image","twitter_misc":{"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"7\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/","name":"User Story Testing: From Stories to Testable Outcomes","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-02-25T10:36:03+00:00","dateModified":"2026-03-02T09:14:03+00:00","description":"Master user story testing with real-world techniques. Learn how acceptance criteria fuel agile testing and how QA teams collaborate to ensure every story delivers value and quality.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/user-story-testing-agile\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"How to Write Effective User Stories","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/"},{"@type":"ListItem","position":3,"name":"From Story to Delivery","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-delivery\/"},{"@type":"ListItem","position":4,"name":"Integrating User Stories with Testing and QA"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website","url":"https:\/\/skills.visual-paradigm.com\/ja\/","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","url":"https:\/\/skills.visual-paradigm.com\/ja\/","logo":{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills\u65e5\u672c\u8a9e"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/1119","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":2,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/1119\/revisions"}],"predecessor-version":[{"id":2432,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/1119\/revisions\/2432"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/1115"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=1119"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=1119"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}