Experiments and Tests

AcaTrove's experiments and tests feature gives labs a structured way to plan, execute, and document research activities. Experiments organize the high-level workflow, while tests capture the detailed execution with discrete steps, runs, and formal signoffs.

Experiments

An experiment represents a planned research activity -- a series of related tasks that together produce a result. Examples include a cell culture assay, a behavioral study session, a computational simulation, or a field sampling campaign.

Creating an Experiment

1. Open your lab and navigate to the Experiments tab.
2. Click New Experiment.
3. Fill in the details:
   • Title -- A clear name for the experiment.
   • Description -- The purpose, hypothesis, or protocol summary.
   • Assigned Members -- Lab personnel responsible for execution.
   • Start and End Dates -- The planned timeframe.
4. Click Create.

Adding Tasks to Experiments

Each experiment can contain multiple tasks. Tasks break the experiment into actionable steps:

1. Open the experiment and click Add Task.
2. Enter the task title, description, and assignee.
3. Set a due date and priority level.
4. Save.

Tasks within an experiment follow the same status workflow as project tasks: To Do, In Progress, and Done.

Dependencies

Tasks within an experiment can have dependencies, ensuring they are completed in the correct order. For example, "Prepare samples" must be completed before "Run analysis." To add a dependency, open a task, click Add Dependency, and select the prerequisite task.

Dependencies are displayed visually in the experiment timeline, making it easy to see the critical path through your experiment.

Experiment detail page showing tasks with dependencies

Tests

Tests are a more formal construct than tasks. A test represents a specific procedure that must be executed according to defined steps, often with quality control requirements. Tests are ideal for standardized assays, instrument calibrations, compliance checks, and any procedure that requires documented proof of completion.

Creating a Test

1. Within an experiment (or directly from the Experiments tab), click New Test.
2. Enter the test name and description.
3. Define the steps -- an ordered list of instructions that must be followed during execution.
4. Specify signoff requirements -- which lab members must approve the test results.
5. Save.

Test Steps

Each test contains an ordered list of steps. A step includes:

• Instruction -- What the technician or researcher must do.
• Expected Result -- What a successful outcome looks like.
• Actual Result -- Filled in during execution to document what actually occurred.
• Pass/Fail -- Whether the step met expectations.

Steps ensure consistency across runs and create a documented record of exactly what was done.

Test Runs

A single test can be executed multiple times. Each execution is recorded as a test run. This is essential for experiments that require replicates, time-series measurements, or iterative optimization.

To start a new run:

1. Open the test and click New Run.
2. Work through each step, recording actual results and pass/fail status.
3. When all steps are complete, submit the run for signoff.

Test run showing steps with actual results and pass/fail status

Signoffs

Signoffs provide formal approval for completed test runs. When a run is submitted, designated signatories receive a notification. Each signatory reviews the results and either approves or rejects the run. Rejected runs can be annotated with feedback, prompting a re-run or corrective action.

Signoff records are immutable -- once approved, the approval cannot be revoked, creating an auditable trail of quality control.

Tips

• Use experiments for the overall workflow and tests for individual procedures that require formal documentation.
• Define steps in advance, even for flexible experiments. Having a template ensures nothing is overlooked during execution.
• Require signoffs for any test that produces data used in publications or regulatory submissions. The audit trail protects your lab's credibility.