# Cro System Testing

> CRO drug clinical trial information system business and system testing context. Use when Codex needs to understand this CRO web system, analyze requirements, design system test plans/cases, execute exploratory testing, classify modules, or write defect reports for sampling, project, billing, logistics, sample, sample-bank, report, consumables, GH, supplier, and related multi-role workflows.

- Skill: `bigassulike/cro-system-testing` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add bigassulike/cro-system-testing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bigassulike/cro-system-testing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: bigassulike (https://skillmd.com/u/bigassulike)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/bigassulike/cro-system-testing

---


# CRO System Testing

## Core Context

Use this skill as the persistent product map for the CRO system, also called the drug clinical trial information system. Treat it as a multi-role, multi-module web system for clinical trial sample collection, project configuration, logistics booking, sample lifecycle, sample-bank storage, report signing/querying, billing, consumables, GH, suppliers, and operational messages.

When the user provides new screenshots or requirements, update the module map and test focus instead of treating the system as a generic admin后台.

## Testing Workflow

1. Identify the module and page from the left navigation, breadcrumb, tab, and visible table/form fields.
2. Map the request to the likely business flow: project setup -> sampling/order -> logistics -> sample receipt/split/storage -> testing/report -> billing/settlement.
3. Derive test points across function, workflow status, permissions/roles, data validation, query/export, audit trail, and exception handling.
4. For defects, write reproduction steps with account role, page path, test data, actual result, expected result, severity, and evidence needed.
5. If screenshots are the only source, state assumptions clearly and ask for missing business rules only when needed.

## Known Navigation

Primary left navigation observed:

- Messages
- Base/basic data
- Sampling
- Project
- Billing
- Transport
- Booking/reservation
- Sample
- Sample bank
- Report
- Consumables
- GH
- Supplier
- Cloud finance/integration

Common top controls:

- Home icon, full-screen icon, breadcrumb path
- A show-complete-info toggle on many list pages
- CRO mini-program entry
- Logged-in user menu, currently observed as an administrator account

## Module Summary

Read `references/module-map.md` when detailed module/page fields are needed.

High-level module responsibilities:

- Sampling info: sample information entry, records, change records, review, push records, reminder notices.
- Project management: research project setup, centers, visit periods, project settings, virtual split settings, report templates, threshold settings, alerts, contracts, group management.
- Billing management: fee categories, service names, invoice info, accounts, settlement settings, settlement records, bill settlement and summaries.
- Logistics booking: sample/consumable logistics orders, statuses, address/box management, price/bill, return orders.
- Sample management: split groups, unsplit/no-need split, virtual split, pending receive, handover, inbound/outbound storage, status query, tube merge/split configuration.
- Sample-bank management: CRO/GH sample-bank info, freezer/box/cabinet management, sample positioning, occupancy visualization.
- Reports: report query/download/export/hide, electronic signature, GH/CRO signing tasks, logs, recheck/additional tests, NGS upload, monthly reports.
- Consumables management: consumables dictionary, management, package management, consumables order, barcode records.

## Test Heuristics

Always consider:

- Role and permission differences: administrator, project manager, business administrator, PM, supplier owner, center/research users if present.
- Status transitions: draft, submitted, pending review, assigned, in delivery, signed/received, canceled, abnormal order, inbound/outbound states.
- Data privacy masking: phone numbers, emails, patient/sample identity fields often appear masked.
- Required clinical identifiers: project number, protocol number, application form, submitting hospital, center number, subject number, random number, name initials, birth date, sex, age, visit period, sample type, collection time.
- Traceability: order numbers, sample barcodes, application forms, logistics tracking, signing logs, audit/change records.
- Export/download behavior: Excel, PDF, logistics manifests, receiving documents.
- Bulk operations: batch entry, batch import, batch review, import overweight/cancel/dedicated-person-or-vehicle.
- Edge cases: duplicate barcode/order, invalid date ranges, missing required fields, status mismatch, permission bypass, masked data leakage, stale filters, pagination with large data.

## Output Style

For test design, prefer tables with: module, scenario, preconditions, steps, expected result, priority, test data.

For exploratory execution reports, prefer: tested scope, environment/account, findings, defect list, blocked items, residual risks.

For defects, use: title, severity, priority, module/page, precondition, steps, actual result, expected result, evidence, suspected impact.