QA Test Scenarios

Manual test scenarios generated from tracked changes. Pass/Fail and Notes are filled in by a tester while actually running each test.

Test	Source	Precondition	Steps	Expected Result	Pass/Fail	Notes
Build a product's hub with a custom introduction	capstone-platform#2 CIP-2	Access to the Config page for a product other than Retail POS that has help articles. Note whether the product already has Release Notes and QA Test Scenarios pages.	Open the Config page for the product. In the Help hub introduction box, enter an introduction of your choice (under 600 characters) and save. Use Create or refresh the hub page for this product. Open the product's hub page.	The hub shows the introduction you entered, a Platform output section that links the product's Release Notes and QA Test Scenarios pages (where those pages exist), and a Documentation section listing the product's help articles. The Help hub introduction box does not accept more than 600 characters.
Hub uses the default introduction when the box is blank, and titles with special characters show exactly	capstone-platform#2 CIP-2	A product other than Retail POS whose Help hub introduction is empty, with at least one help article whose title contains & or <.	Open the Config page for the product and confirm the Help hub introduction box is empty. Use Create or refresh the hub page for this product. Open the product's hub page and read the introduction. Find the help article whose title contains & or < in the Documentation section.	The introduction reads: "Release notes, help articles and QA scenarios for <product name>, drafted by the Change Intelligence Platform from the product's changes and reviewed by a person before they are published." with the product's name filled in. The article title appears exactly as written, including the & or < characters.
Retail POS demo hub is unchanged	capstone-platform#2 CIP-2	Note how the Retail POS hub looks before the change ships.	Use Create or refresh the hub page for Retail POS. Open the Retail POS hub page.	The Retail POS demo hub looks the same as before.
Default product is marked, must stay active, and the dashboard opens on it	capstone-platform#2 CIP-2	At least two active products exist; Retail POS is the default.	Open the Config page and find Retail POS. Check how Retail POS is labeled. Try to make Retail POS inactive. Open the dashboard fresh, without having picked a product. Pick a different product in the Product picker.	Retail POS is marked (default product). Making it inactive is refused, and the Config page explains: "This is the default product, which the dashboard opens on, so it must stay active." The dashboard opens on Retail POS until another product is picked in the Product picker, after which it shows the picked product.
Command run without –department falls back to the default product	capstone-platform#2 CIP-2	Ability to run platform commands; more than one product is active and Retail POS is the default.	Run a command without the –department option. Read the command's output.	The command uses Retail POS and says: "No product named: using the default product, retail-pos (pass –department <slug> for another)." If only one product is active, the command uses that product instead.
Config form shows three sections with a connection picker for each kind	capstone-platform#3 CIP-3	Signed in with access to the Config page. At least one GitHub, one Atlassian and one WordPress connection exist, ideally including one failing connection, and for one kind only a single connection exists.	Open the Config page and start creating a new product. Look at how the form is arranged. Open the GitHub connection picker and review its options. Open the Atlassian (Jira and Confluence) connection picker and review its options. Switch on an output that publishes to WordPress, then open the WordPress connection picker and review its options.	The form has three sections: Product (Name, Slug, Active), Where changes come from (GitHub connection and repositories, Atlassian connection and Jira project key) and Where output goes (the four output switches and what they need). Each picker lists only connections of its own kind. A failing connection is marked "(failing)". For a kind with only one connection, the new product starts with that connection already selected.
Fields appear only while the outputs that need them are on	capstone-platform#3 CIP-3	Signed in and editing a product on the Config page.	Switch Internal release notes on and check whether Confluence space key is shown. Enter a value in Confluence space key. Switch Internal release notes off and check whether Confluence space key is shown. Switch Internal release notes back on and look at the Confluence space key value. Switch on an output that publishes to WordPress and check which fields appear. Switch all outputs that publish to WordPress off and check those fields again.	Confluence space key is shown only while Internal release notes is on, and when it reappears it still holds the value entered earlier. WordPress connection, WordPress hub page title and Help hub introduction (optional) are shown only while an output that publishes to WordPress is on.
All problems are listed under Before you can save and Save changes stays disabled	capstone-platform#3 CIP-3	Signed in. An existing product has Internal release notes and Customer release notes switched on. Another product (for example Retail POS (demo)) already owns a repository such as acme/shared.	Open the existing product for editing on the Config page. Switch Internal release notes off while Customer release notes stays on. Look under Before you can save and at the Save changes button. Switch Internal release notes back on and leave Confluence space key empty. Add the repository already owned by the other product. Look under Before you can save again. Fix each listed problem one at a time, watching Save changes.	Problems appear together under Before you can save before anything is saved, for example "Customer release notes needs Internal release notes switched on.", "Enter the Confluence space key: an output that is switched on publishes there." and "acme/shared already belongs to Retail POS (demo). A repository can belong to only one product." Save changes stays disabled until no problems remain, and nothing is saved while it is disabled.
Read-only view wording for repositories and an empty help hub	capstone-platform#3 CIP-3	A product with one repository tracked by release and one repository with hand-picked pull requests. A help hub that has no articles yet.	Open the product's read-only view on the Config page and look at each repository's description. Open the help hub that has no articles yet.	The repository tracked by release says "tracked by release" instead of "0 PRs", and the other says "N hand-picked pull requests" with its count. The empty help hub says "Articles appear here as the platform publishes them."
Choose Jira project and Confluence space from live dropdowns	capstone-platform#4 CIP-4	A product exists with a working Atlassian connection that can see at least one Jira project and one Confluence space. The tester can open the Config page.	Open the Config page for the product. Open the Jira project dropdown and look at the entries. Type part of a project key or name into the box. Pick a project from the filtered list. Repeat the previous three steps for the Confluence space dropdown.	Both dropdowns list the projects and spaces the Atlassian connection can see, each shown as "KEY: Name" (for example "CIP: Change Intelligence Platform"). Typing filters the list, and the chosen entry is held in the field. If a key that the connection cannot see was saved earlier, it still appears as a choice, marked "(this connection cannot see it)".
Choose WordPress hub page or name a new one	capstone-platform#4 CIP-4	A product exists with a working WordPress connection to a site that has published top-level pages.	Open the Config page for the product. Open the WordPress hub page dropdown and review the entries. Select an existing page. Open the dropdown again and select "A new page…".	The dropdown lists the site's published top-level pages plus "A new page…". Selecting "A new page…" asks for a "New hub page title".
Choose GitHub repositories and add one by its address	capstone-platform#4 CIP-4	A product exists with a working GitHub connection that can read at least one repository. The tester knows the address of one repository the connection can read and one owner/name that it cannot read or that does not exist.	Open the Config page for the product. Look at the GitHub repositories list and choose a repository from it. In "Add a repository by its address", paste a full address such as https://github.com/owner/name (or a link to a pull request in that repository) for a readable repository. In "Add a repository by its address", enter an owner/name that the connection cannot read. Open "Advanced: hand-picked pull requests, priority and stack", add a line for a repository that is not chosen, and look at the save area. Click "Refresh lists".	The repositories list holds the repositories the GitHub connection can read. The readable address is checked against GitHub and the page says "Added owner/name." The unreadable entry is refused with a reason such as "GitHub has no repository owner/name that this connection can read." Hand-picked pull requests, priority and stack appear under the Advanced section. A line there for a repository that is not chosen is listed under "Before you can save". "Refresh lists" reads the lists again.
Field falls back to typing when a list cannot be read	capstone-platform#4 CIP-4	A product whose Atlassian connection cannot read the project list, for example because its credentials are invalid so that Jira answers with HTTP 401.	Open the Config page for the product. Look at the Jira project field.	The Jira project field is a box to type in, with a note explaining why, for example "Type the Jira project key: the list could not be read. Jira answered with HTTP 401."
Product with no GitHub repository shows the not-set-up box	capstone-platform#5 CIP-5	A product exists that has no GitHub repository chosen. The tester can select this product in the sidebar.	Select the product in the sidebar. Open the Generate page. Open the Review page. Open the Publish page. On any of these pages, click Open Config.	On Generate, Review and Publish, only a box headed "<product> is not set up yet" is shown (instead of a disabled "Generate drafts for 0 changes" button, a one-line Review page, or "Switched off" tiles). The box lists what is missing and what to do, e.g. "No GitHub repository is chosen. Choose its repositories under Where changes come from." Clicking Open Config opens the settings of the product chosen in the sidebar.
Product with every output switched off shows the not-set-up box	capstone-platform#5 CIP-5	A product exists that has a GitHub repository chosen but every output switched off.	Select the product in the sidebar. Open the Generate, Review and Publish pages in turn.	Each page shows only the "<product> is not set up yet" box, listing that the outputs are switched off and what to do about it.
Product with a failing connection shows the needs-attention box above the normal page	capstone-platform#5 CIP-5	A product that is otherwise set up, where the GitHub connection is failing its check, and some drafts exist to review.	Select the product in the sidebar. Open the Generate, Review and Publish pages in turn. On the Review page, confirm the drafts are still shown below the box. Click Open Connections.	A box headed "<product> needs attention" appears above the normal page content, with a message such as "The GitHub connection is failing its check. Open it on the Connections page and check it." Drafts can still be reviewed underneath. An Open Connections button is shown and takes the tester to the Connections page.
Fully set-up product sees pages unchanged, and picker info icons explain shared lists	capstone-platform#5 CIP-5	A product that is fully set up with working connections.	Select the product in the sidebar. Open the Generate, Review and Publish pages. Open the product's Config settings. Hover over or open the info icon next to the Jira project picker. Do the same for the Confluence space picker.	No setup or attention box appears; the pages look exactly as before. The info icons say the list holds everything the Atlassian connection can see, including projects and spaces other products use, and that choosing one changes only this product.
Connections page shows every connection as stored with full controls	capstone-platform#7 CIP-7	The updated app is deployed and rebooted. The connections Retail POS Demo (GitHub), CIP and KAN Atlassian, and Demo Publishing Site WordPress have been added on the Connections page.	Open the Connections page. Review the list of connections. For each connection, look at its storage label and the available controls.	No connection named "(deployment default)" is listed, and no "Deployment secrets" label appears. Every connection is shown as "Stored, encrypted" and offers both Replace credentials and Delete connection, whatever its kind (GitHub, Atlassian, WordPress).
Products work end to end through the added connections	capstone-platform#7 CIP-7	The updated app is deployed. Retail POS (demo) and Change Intelligence Platform are pointed on Config at the connections added on the Connections page.	On Config, run Check connection for each connection used by Retail POS (demo) and Change Intelligence Platform. Run Sync, Generate and Publish for Retail POS (demo). Run Sync, Generate and Publish for Change Intelligence Platform.	Each connection passes Check connection. Sync, Generate and Publish all succeed for both products using the added connections.
Product with no chosen connection starts on the oldest connection of the right kind	capstone-platform#7 CIP-7	At least two connections of the same kind exist on the Connections page, and you know which one was added first. A product has no connection chosen for a job that uses that kind.	Open Config for that product. Look at which connection the job starts on.	The job starts on the oldest connection of the right kind.
Annotated screenshots appear under steps in the five updated help articles	capstone-platform#9 CIP-9	The screenshots have been placed in the live help articles. Open the published help site on a desktop browser.	Open the help article "Bringing in Changes". Scroll through the numbered steps and look under each step. Repeat for "Generating Drafts", "Reviewing Drafts", "Publishing Approved Drafts" and "Connecting Your Tools".	Each article shows screenshots placed right after the steps they belong to. The screenshots are in the platform's teal style with stamps, boxes, arrows and cursors. The images look sharp, are indented under their step, and are never wider than the text column. The old low-resolution images are gone, and the article text is otherwise unchanged. "Publishing Approved Drafts" shows only a screenshot for the sidebar step.
Help article with screenshots displays without sideways scrolling on a phone-width screen	capstone-platform#9 CIP-9	Use a phone, or a browser window narrowed to 375 pixels wide.	Open the help article "Bringing in Changes". Scroll through the whole article, including all of its screenshots. Try to scroll the page sideways.	The article shows its 7 screenshots. All of them fit within the text column, and the page does not scroll sideways.
Articles left out of the update keep their existing content	capstone-platform#9 CIP-9	Open the published help site on a desktop browser.	Open the help article "Finding Your Way Around" and look at its screenshots. Open the help article "Setting Up a Product" and look at its screenshots.	"Finding Your Way Around" still shows its existing screenshot, not a new captured one. "Setting Up a Product" has not received new step screenshots as part of this change.
Sidebar pipeline items are unnumbered and joined by a line	capstone-platform#10 CIP-14	The app has been restarted after the update and the dashboard is open.	Look at the pipeline items in the sidebar. Click Generate and note the sidebar and the page title. Click Review and note the sidebar and the page title. Click Publish and note the sidebar and the page title.	The sidebar items read Generate, Review and Publish, with no numbers. A thin line runs through their icons, joining them and showing the order. Release candidate sits beside the line, under Generate. The current step stays highlighted as you move between pages, and each page title matches its sidebar label with no number.
Sync sources box is headed 'Settings for' with the product name set apart	capstone-platform#10 CIP-14	At least one product is set up. The app has been restarted after the update.	Open the Generate page. Find the Sync sources box and read its heading.	The box is headed Settings for, followed by the product's name. The name is shown in its own color and case, so it is clearly separate from the heading and does not read as part of the same phrase.
Ingest a release uses the 'Release cut name' label	capstone-platform#10 CIP-14	The app has been restarted after the update.	Open the Ingest a release form. Find the field for naming the cut.	The field is labeled Release cut name. The old label, Name of this cut, no longer appears.
Disabled Delete connection explains what to do	capstone-platform#10 CIP-14	A connection exists that is used by at least one product.	Open Connections. Find the connection that a product uses and look at its Delete connection option.	Delete connection is disabled and shows this explanation: "To delete it, open Config, choose a different connection for each of those products, then come back here."
Screenshot check reports problems in the current help articles	capstone-platform#11 CIP-15	A checkout of the tool containing this change. The five live help articles are in their state before the rewrite, and the help/placements.json file is present.	Open a terminal in the project folder. Run: python -m change_intel screenshot-check help/placements.json Read the report for each live article. Confirm the help article files were not modified by running the command.	The command reports problems for each live article. These cover steps with no screenshot, lettered lists without a lettered screenshot or with letters on the wrong parts, screenshots that mark something their step doesn't name, and step numbers on images that sit under their own step. In total, 43 problems are listed. The command only reports and does not change any files.
Finding Your Way Around shows the lettered sidebar screenshot	capstone-platform#12 CIP-16	Access to the platform's published help pages in WordPress.	Open the published Finding Your Way Around help page. Locate the sidebar screenshot. Compare the sidebar labels in the screenshot with the article text.	The sidebar screenshot uses A–F letter labels, not the old numbered labels.
Bringing in Changes and Generating Drafts follow the new layout	capstone-platform#12 CIP-16	Access to the platform's published help pages in WordPress.	Open the published Bringing in Changes help page. Check each step for a screenshot beneath it. Check that the sections are lettered and that the Release candidate page screenshot uses lettered labels. Open the published Generating Drafts help page. Check that concepts are presented as bullets and that each step has a screenshot. Look for the panel explaining why there are two release notes.	Bringing in Changes has a screenshot under every step, lettered sections, and lettered labels on the Release candidate page screenshot. Generating Drafts shows concepts as bullets, a screenshot per step, and the "why two release notes" panel.
Connecting Your Tools shows the lettered card, per-step screenshots and delete callout	capstone-platform#12 CIP-16	Access to the platform's published help pages in WordPress.	Open the published Connecting Your Tools help page. Find the connection card screenshot and check its labels. Go through the steps for adding a connection and check each one for a screenshot. Find the callout about deleting a connection.	The connection card is labeled with letters, every step of adding a connection has a screenshot, and a callout about deleting a connection is present.
Lettered option lists stay as one continuous list	capstone-platform#12 CIP-16	Access to the four republished help pages in WordPress.	Open each of the four republished help pages. Find any lists of lettered options. Check the lettering of each list from start to finish.	Each set of lettered options appears as one continuous A, B, C list, without restarting the lettering partway through.
Letter stamps are larger with a soft shadow in live help articles	capstone-platform#13 CIP-17	Access to the four live help articles that were re-captured and republished (pages 249, 252, 253, 261).	Open each of the four live help articles. Find screenshots that carry letter or number stamps (the A, B, C or 1, 2, 3 circles). Compare each stamp's height with the capital letters of the section heading text beside it. Look at the edges of each stamp and the edges of the screenshot around it.	Stamps are a few pixels taller than the heading's capital letters beside them. Each stamp carries a soft drop shadow, and the shadow is not cut off by the edge of the screenshot.
Sync sources screenshot has no overlapping boxes	capstone-platform#13 CIP-17	Access to the live help article that contains the Sync sources screenshot.	Open the help article containing the Sync sources screenshot. Look at the highlight boxes and arrow on the screenshot. Check whether any box edge runs through another box or its text. Also look over the other highlighted screenshots in the four live articles for boxes that touch or overlap.	On the Sync sources screenshot, the Settings for panel is boxed, and an arrow points at its Change these on the Config page link. No box overlaps another, and a gap remains between neighboring boxes in all four articles.
Capture refuses marks too close to box, and the screenshot check uses the help manifest	capstone-platform#13 CIP-17	Ability to run the screenshot capture tool and screenshot-check. You also need a shot that marks two elements with boxes that sit too close together to box both.	Run the capture for the shot with the two too-close boxed elements. Read the message shown, and check whether an image file was saved for that shot. Run screenshot-check help/articles.json.	The capture fails with a message naming both marks, and no image is saved for that shot. screenshot-check reads help/articles.json and reports all four articles OK.
Review card shows existing and missing screenshots	capstone-platform#14 CIP-18	A documentation draft is open for review in the dashboard. It contains Screenshot lines under its steps: at least one names a screenshot that already exists in the published articles, and at least one names a new screenshot that has not been captured yet.	Open the draft's Review card in the dashboard. Find the step with the screenshot that already exists. Find the step with the screenshot that has not been captured. Look at the chip on the card that counts screenshots. Read the card's note about approving and publishing.	The existing screenshot appears as its actual image. The missing one appears as a dashed "Screenshot needed" box showing its name. The chip shows how many screenshots are still to capture. The card says the draft can be approved now and is published once every screenshot exists.
Publish to WordPress waits for missing screenshots	capstone-platform#14 CIP-18	Two approved documentation drafts: one with at least one missing screenshot, and one where every screenshot exists. Access to the WordPress help site to check the result.	Use Publish to WordPress on the draft with a missing screenshot. Read the message shown. Check the WordPress help site for that article. Use Publish to WordPress on the draft where every screenshot exists. Check the WordPress help site for that article.	The draft with a missing screenshot stays unpublished, nothing is changed in WordPress, and the message says why, naming which screenshots are missing. The draft with all screenshots is published with its images placed.
publish-help refuses to overwrite a page edited in WordPress	capstone-platform#14 CIP-18	Access to run the publish-help tool against the live help pages. One live help page has been edited directly in WordPress since publish-help last published it.	Run publish-help. Read its output for the edited page. Check the help/backups folder. Copy the WordPress edits into the source for that page, then run publish-help with –replace-edited followed by that page.	Before writing, publish-help backs up each live page into help/backups. It refuses to replace the page that was edited in WordPress since it last published it. When run with –replace-edited for that page, it replaces the page.
Publish page describes the product's own destinations	capstone-platform#15 CIP-13	At least one product with internal publishing to Confluence (a known space key) and customer publishing to a WordPress hub (a known hub title) switched on. The tester can open that product's Publish page.	Open the Publish page for the product. Read the subtitle, the caption, the release-name field label, the button text, and the lines on each card. Open the Publish page for a second product with different destinations, and compare.	The release-name label no longer says "(the Confluence page title)". The cards no longer say "the WordPress hub" or "the QA Test Scenarios table on the WordPress hub". Each card shows one short line per destination, built from the product's own settings, for example "Internal: Confluence, space <space key>" and "Customers: WordPress, under <hub title>", using that product's actual space key and hub title. The second product's page shows its own destinations.
Switched-off channel is neither described nor named	capstone-platform#15 CIP-13	A product with one publishing channel switched off, for example customer publishing to WordPress off while internal publishing to Confluence is on. The page is viewed in read-only mode.	Open the Publish page for that product. Read the cards, the subtitle, the caption, and the read-only notice.	No card line describes the switched-off channel. The read-only notice names only the tools that are in use, so the tool for the switched-off channel (WordPress in this example) is not mentioned.
Card buttons stay on one line at wide widths	capstone-platform#15 CIP-13	A product whose hub title is long enough to wrap onto more than one line in its card. A browser window that can be resized.	Open the product's Publish page with the browser window 1400 px wide. Check the buttons on each card and whether the page scrolls sideways. Resize the window to 1120 px wide and check again.	At both widths, the three buttons stay on one line and line up across cards, even where the hub title wraps. The page has no sideways scroll.