A first week for a new tester

Integration Core help · for a new tester · graded against Core v1.0.0-rc.5 · written 2026-10-06 · re-read against rc.8's screens 2026-10-09 · where a newer Core words a screen differently, see the Glossary's "Changed in newer releases"

An ordered first week for someone who will learn and test the whole solution — Integration Core, WooCommerce and Acumatica. Each day is about an hour of reading and an hour on the screens, and ends with the connectors' beta test plans. You need a user on the beta site with the Integration Viewer role to look, or Integration Manager to press buttons — and, for the connectors' test plans, the iVendNext roles each plan lists. Ask whoever runs the beta.

Day 1 — the shape of the product

1. Read How Integration Core works: what Core is and is not, a record and its tries, and the states.
2. Read the section Unverified: we cannot tell if it arrived twice. It is the one idea that protects money: a record we cannot confirm is never sent again, and is never called failed.
3. On the beta site, open Integrations Hub. Find the six tiles and the cards. Match each to its line in the Glossary.

You are done when you can say, without notes, what Unverified, Waiting and Needs a decision each mean and what an operator does about each.

Day 2 — the connections

1. Read the Glossary sections on the coloured words on a connection and on the Hub's cards.
2. On the beta site: Connections → open each connection. Read its coloured word, the messages at the top, who last switched it, and its Check Every (minutes).
3. Open Connection Health. Compare each line with the Connections list.

You are done when you can explain why a connection that reads Not reported yet raises no alert, and why the green word is not proof at go-live.

Day 3 — the daily habit

1. Read Daily operations from top to bottom.
2. On the beta site, do the daily look in its order: Connection Health, then Failed, Cannot tell if it arrived, Needs a decision, Reversals not confirmed, Money records waiting, Set aside.
3. Open one record from each that has rows. Read the sentence at the top and find which buttons it offers — and which it does not.

You are done when you can say what each button does and what it does not do.

Day 4 — when something goes wrong

1. Read Troubleshooting, using its Find your symptom table.
2. Read the connectors' own troubleshooting: Acumatica's Troubleshooting (docs/guides/TROUBLESHOOTING.md in ivendnext/ivendnext_acumatica). WooCommerce's Troubleshooting (docs/guides/TROUBLESHOOTING.md in ivendnext/iVendNext_WooCommerce) and its Support runbook (docs/beta/SUPPORT_RUNBOOK.md).
3. On the beta site, find one waiting record and read its Waiting on: reason. Which setup would clear it?

You are done when you can tell, from what the screen says, whether a problem is Core's or a connector's.

Day 5 — how it is put in, and what it promises

1. Read Implementing an integration — Part 1, then Acumatica's Connect your Acumatica (Part 2) and What syncs today.
2. Read the bounds at the end of Part 1's Hand over to support: what Integration Core does not do.
3. Read Acumatica's Known issues (docs/beta/KNOWN_ISSUES.md), so you do not report a known limit as a defect.

You are done when you can explain to a customer what Integration Core does, in two sentences, and name two things it does not do.

Then — the connectors' beta test plans

Run the scenarios in each connector's beta test plan, in the order it gives:

• Acumatica: Acumatica connector — beta test plan (docs/beta/BETA_TEST_PLAN.md in ivendnext/ivendnext_acumatica). Its first line says it is a published copy; its section Known limits lists what not to report.
• WooCommerce: WooCommerce connector — beta test plan (docs/beta/BETA_TEST_PLAN.md in ivendnext/iVendNext_WooCommerce), a published copy like Acumatica's.

Report the way each test plan's Where to report section says, with what it asks for; Troubleshooting → What to send with a ticket lists what support will also need.

Known Core limits at rc.5 — not defects

Do not report these as new; each is known and recorded.

• A connection chip's hover text reads Document is in draft state on every row — the framework's.
• The Link manually dialog lists record types as keys (tax_rate) — words in the next release.
• A list reached from a Hub card keeps the filters you last used there — check the filter pills.
• An incoming record with no order number recorded yet is titled by its own ID (Order j2nudlqff3), on the list and on its form — read the order number on its Incoming Record (ID in Connected System).
• An old record's stored sentence names an old button or tile (Keep ours, Needs a Person) — read it with today's names (Keep iVendNext Version, the Failed tile).
• One order the connection cannot import shows many Retrying rows — Troubleshooting, One order shows many Retrying rows.
• Stopped part-way never lights for either shipped connector at rc.5.

Source: the known issues §2 and §5 (2026-10-02); the support runbook §10 (2026-10-02); the latest walk's findings (IC-E2E-WALK RUN 6, IC-E2E6-B3/-B4).