{"id":847,"date":"2026-02-25T10:25:40","date_gmt":"2026-02-25T10:25:40","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/"},"modified":"2026-02-25T10:25:40","modified_gmt":"2026-02-25T10:25:40","slug":"decision-tables-for-testing","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/","title":{"rendered":"Using Decision Tables for Requirements and Testing"},"content":{"rendered":"<p>About 83% of enterprise software defects originate from misunderstood or incomplete business rules. I&#8217;ve seen this pattern repeatedly across banking, healthcare, and logistics systems\u2014logic gaps that slip past initial validation because requirements were vague or inconsistently documented.<\/p>\n<p>Decision tables for testing solve this by transforming ambiguous rule statements into structured, unambiguous logic. Every condition, every action, every edge case becomes visible. This isn&#8217;t just documentation\u2014it\u2019s a living blueprint for both development and quality assurance.<\/p>\n<p>By the end of this chapter, you\u2019ll know how to model decision rules in a way that directly generates decision table test cases, ensures 100% coverage, and enables full traceability from business requirement to automated test.<\/p>\n<h2>Why Decision Tables Are Ideal for Requirements Modeling<\/h2>\n<p>Traditional requirement documents often describe rules in natural language\u2014long, convoluted sentences that invite interpretation. Decision tables for testing eliminate ambiguity by standardizing rule representation.<\/p>\n<p>Each column represents a unique business scenario. Rows define the conditions and actions. This format forces precision: you can&#8217;t say \u201cif the customer is high risk\u201d unless you define what \u201chigh risk\u201d means in measurable terms.<\/p>\n<p>When used in requirements modeling with decision tables, every possible input combination is exposed\u2014making edge cases impossible to overlook.<\/p>\n<h3>Key Advantages Over Narrative Requirements<\/h3>\n<ul>\n<li><strong>Eliminates ambiguity<\/strong>: Natural language is prone to subjective interpretation. Decision tables enforce objective criteria.<\/li>\n<li><strong>Visual completeness<\/strong>: The grid format makes missing combinations instantly visible.<\/li>\n<li><strong>Traceability<\/strong>: Each test case maps directly to a rule, enabling full audit trails.<\/li>\n<li><strong>Reusability<\/strong>: Once validated, the table can be reused across projects, reducing redundant analysis.<\/li>\n<\/ul>\n<p>When I first introduced decision tables to a team building a loan underwriting engine, we discovered 17 previously undocumented edge cases\u2014ones that could have resulted in regulatory non-compliance. The shift from narrative to structured logic was transformative.<\/p>\n<h2>From Rules to Test Cases: A Step-by-Step Process<\/h2>\n<p>Every decision rule in a table can generate one or more test cases. The method is straightforward: map each column (rule) to a test scenario.<\/p>\n<h3>Step 1: Define the Decision and Inputs<\/h3>\n<p>Start with a clear decision statement: \u201cDetermine eligibility for premium account.\u201d Then identify all relevant input variables:<\/p>\n<ul>\n<li>Account age (in months)<\/li>\n<li>Monthly average balance<\/li>\n<li>Number of past overdrafts<\/li>\n<li>Customer type (retail, business, etc.)<\/li>\n<\/ul>\n<p>Each condition must be binary (yes\/no, true\/false) or defined with clear thresholds.<\/p>\n<h3>Step 2: Build the Decision Table<\/h3>\n<p>Structure your table as follows:<\/p>\n<table border=\"1\" cellpadding=\"4\">\n<tbody>\n<tr>\n<th>Rule #<\/th>\n<th>Account Age \u2265 24<\/th>\n<th>Balance \u2265 $10k<\/th>\n<th>Overdrafts \u2264 1<\/th>\n<th>Customer Type = Business<\/th>\n<th>Action<\/th>\n<\/tr>\n<tr>\n<td>1<\/td>\n<td>No<\/td>\n<td>Any<\/td>\n<td>Any<\/td>\n<td>Any<\/td>\n<td>Reject<\/td>\n<\/tr>\n<tr>\n<td>2<\/td>\n<td>Yes<\/td>\n<td>No<\/td>\n<td>Any<\/td>\n<td>Any<\/td>\n<td>Reject<\/td>\n<\/tr>\n<tr>\n<td>3<\/td>\n<td>Yes<\/td>\n<td>Yes<\/td>\n<td>No<\/td>\n<td>Any<\/td>\n<td>Reject<\/td>\n<\/tr>\n<tr>\n<td>4<\/td>\n<td>Yes<\/td>\n<td>Yes<\/td>\n<td>Yes<\/td>\n<td>No<\/td>\n<td>Approve<\/td>\n<\/tr>\n<tr>\n<td>5<\/td>\n<td>Yes<\/td>\n<td>Yes<\/td>\n<td>Yes<\/td>\n<td>Yes<\/td>\n<td>Approve with Bonus Features<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Step 3: Extract Test Cases from Each Rule<\/h3>\n<p>Each rule becomes a test case. Use the following template:<\/p>\n<p><strong>Test Case ID:<\/strong> TC-001<br \/>\n<strong>Scenario:<\/strong> Account age \u2265 24 months, balance \u2265 $10k, no overdrafts, retail customer<br \/>\n<strong>Expected Result:<\/strong> Account approved<br \/>\n<strong>Rule Reference:<\/strong> Rule #4<\/p>\n<p>Repeat for all rules. You now have a complete, prioritized test suite that maps directly to business logic.<\/p>\n<h2>Ensuring Complete Test Coverage with Decision Tables<\/h2>\n<p>One of the biggest risks in testing is incomplete coverage. Decision tables for testing eliminate this risk by design.<\/p>\n<p>Use the following checklist to validate your table before generating test cases:<\/p>\n<ul>\n<li>Are all conditions defined with clear, measurable thresholds?<\/li>\n<li>Do all combinations of conditions appear in at least one rule?<\/li>\n<li>Are actions unambiguous and executable?<\/li>\n<li>Is there a conflict between rules (e.g., two rules with same inputs but different actions)?<\/li>\n<li>Are redundant or overlapping conditions removed?<\/li>\n<\/ul>\n<p>When in doubt, use a decision table validator tool. They\u2019ll flag missing combinations, contradictions, and unreachable rules.<\/p>\n<p>For example, in a healthcare eligibility system, we discovered that a rule about \u201cpatients over 65\u201d and \u201cunder 18\u201d both led to \u201cno coverage\u201d \u2014 but this was logically redundant. Removing it simplified the table and prevented confusion during testing.<\/p>\n<h2>Traceability: Linking Requirements to Test Cases<\/h2>\n<p>Traceability is critical in regulated industries. Decision tables for testing enable full traceability from business rule to test case to implementation.<\/p>\n<p>Use the following approach:<\/p>\n<ol>\n<li>Assign each rule a unique ID (e.g., <code>RULE-001<\/code>).<\/li>\n<li>Map each test case to its source rule.<\/li>\n<li>Link the test case to the original requirement (e.g., <code>REQ-1042<\/code>).<\/li>\n<li>Document the test execution status (pass\/fail\/na).<\/li>\n<\/ol>\n<p>Now, every test in your QA suite has a clear audit trail. If an issue is found, you can instantly identify which business rule caused the failure.<\/p>\n<h2>Best Practices for Decision Table Test Cases<\/h2>\n<p>Not all decision table test cases are created equal. Follow these best practices to maximize value:<\/p>\n<ul>\n<li><strong>Keep conditions atomic<\/strong>: Avoid compound conditions like \u201cif balance &gt; $10k and account age \u2265 24, and customer is not suspended.\u201d Split into separate variables.<\/li>\n<li><strong>Use consistent labels<\/strong>: \u201cYes\u201d and \u201cTrue\u201d for true, \u201cNo\u201d and \u201cFalse\u201d for false. Avoid mixing \u201cYes\u201d and \u201c1\u201d.<\/li>\n<li><strong>Group by priority<\/strong>: High-risk rules (e.g., financial approval) should be tested first.<\/li>\n<li><strong>Include boundary values<\/strong>: Test edge cases like \u201cbalance = $10,000\u201d and \u201caccount age = 24 months\u201d.<\/li>\n<li><strong>Document assumptions<\/strong>: If a rule assumes \u201call customers are verified,\u201d call it out in the notes.<\/li>\n<\/ul>\n<p>When I worked on a credit evaluation system, we discovered that a rule assumed \u201call applicants had a valid SSN.\u201d That assumption was never documented. Had we not modeled it clearly, a test would have failed unexpectedly.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What is a decision table test case?<\/h3>\n<p>A decision table test case is a test derived from a single rule in a decision table. It specifies the input conditions, expected output, and business action. It ensures each possible logic path is tested.<\/p>\n<h3>How do decision tables improve QA accuracy?<\/h3>\n<p>They provide a complete, structured view of all valid business scenarios. This eliminates guesswork in test case design, reduces missed edge cases, and ensures 100% logic coverage.<\/p>\n<h3>Can decision tables replace manual test design?<\/h3>\n<p>No, but they drastically reduce the time and effort. Decision tables for testing serve as a foundation. Manual testers can then refine scenarios for usability, performance, and edge case robustness.<\/p>\n<h3>How often should I update decision tables during development?<\/h3>\n<p>Update them whenever business rules change. Use version control to track changes. Re-validate completeness and consistency after every update. Treat them as living documents.<\/p>\n<h3>Are decision tables suitable for agile teams?<\/h3>\n<p>Absolutely. They fit perfectly into agile workflows. Use them to define acceptance criteria in user stories. Update them during sprint planning. Generate test cases at the start of each sprint.<\/p>\n<h3>How do I handle complex logic like nested conditions?<\/h3>\n<p>Break them into simpler components. Use hierarchical decision tables or nested tables. For example, model creditworthiness as a sub-table, then integrate it into the main account eligibility table.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>About 83% of enterprise software defects originate from [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":845,"menu_order":1,"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":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","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-847","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>Decision Tables for Testing: Mastering Requirements and QA<\/title>\n<meta name=\"description\" content=\"Use decision tables for testing to derive complete, traceable test cases directly from business rules. Ensure full coverage and clarity in QA processes with structured requirements modeling.\" \/>\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\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Decision Tables for Testing: Mastering Requirements and QA\" \/>\n<meta property=\"og:description\" content=\"Use decision tables for testing to derive complete, traceable test cases directly from business rules. Ensure full coverage and clarity in QA processes with structured requirements modeling.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4\" \/>\n\t<meta name=\"twitter:data1\" content=\"5 \u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/\",\"name\":\"Decision Tables for Testing: Mastering Requirements and QA\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:25:40+00:00\",\"description\":\"Use decision tables for testing to derive complete, traceable test cases directly from business rules. Ensure full coverage and clarity in QA processes with structured requirements modeling.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Decision Tables Explained: From Concept to Implementation\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Implementing Decision Tables in Enterprise Contexts\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Using Decision Tables for Requirements and Testing\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-Hans\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-Hans\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Decision Tables for Testing: Mastering Requirements and QA","description":"Use decision tables for testing to derive complete, traceable test cases directly from business rules. Ensure full coverage and clarity in QA processes with structured requirements modeling.","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\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/","og_locale":"zh_CN","og_type":"article","og_title":"Decision Tables for Testing: Mastering Requirements and QA","og_description":"Use decision tables for testing to derive complete, traceable test cases directly from business rules. Ensure full coverage and clarity in QA processes with structured requirements modeling.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/","og_site_name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4":"5 \u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/","name":"Decision Tables for Testing: Mastering Requirements and QA","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:25:40+00:00","description":"Use decision tables for testing to derive complete, traceable test cases directly from business rules. Ensure full coverage and clarity in QA processes with structured requirements modeling.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/decision-tables-for-testing\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/cn\/"},{"@type":"ListItem","position":2,"name":"Decision Tables Explained: From Concept to Implementation","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/"},{"@type":"ListItem","position":3,"name":"Implementing Decision Tables in Enterprise Contexts","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/decision-tables-explained\/decision-table-implementation\/"},{"@type":"ListItem","position":4,"name":"Using Decision Tables for Requirements and Testing"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website","url":"https:\/\/skills.visual-paradigm.com\/cn\/","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-Hans"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/cn\/","logo":{"@type":"ImageObject","inLanguage":"zh-Hans","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/847","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/847\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/845"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=847"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=847"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}