> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/resources/test-plan-for-resources.md).

# Test plan for Resources

Use this plan to validate **Resources** end to end.

It covers activation, setup, planning, work orders, and tariffs.

### Test scope

Validate these areas:

* plan and feature availability
* resource categories and resource creation
* Scheduler visibility and planning behavior
* refresh behavior while browsing in the Scheduler
* work order linking
* tariff setup and billing behavior

### Test data set

Use a fixed data set for every test run.

#### Users

* **Admin user** — full rights for setup and activation
* **Planner user A** — can use the Scheduler and work orders
* **Planner user B** — second planner for update checks
* **Field user** — mobile user for work order validation if needed

#### Resource categories

* **Vehicles**
* **Tools**
* **Cranes**

#### Resources

* **RES-TRUCK-01** — category **Vehicles**
* **RES-DRILL-01** — category **Tools**
* **RES-CRANE-01** — category **Cranes**
* **RES-NOCAT-01** — no category

#### Work orders

* **WO-RES-001** — single-day work order
* **WO-RES-002** — overlapping single-day work order
* **WO-RES-003** — work order with billable resource usage

#### Tariff values

* **Hour** — `10`
* **Half-day** — `35`
* **Day** — `60`
* **Week** — `250`

### Execution rules

* Run all tests in the same environment.
* Reset changed records after each run.
* Use the same dates for overlap tests.
* Use two planner sessions for refresh checks.
* Record both expected and actual results.
* Mark blocked tests with the blocking dependency.

### Core test cases

#### Activation and access

| ID      | Scenario                | Test data                 | Expected result                                   |
| ------- | ----------------------- | ------------------------- | ------------------------------------------------- |
| RES-001 | Check plan eligibility  | Account on supported plan | Resources is available for activation or included |
| RES-002 | Activate Resources      | Admin user                | Resources becomes available in the BackOffice     |
| RES-003 | Check user access       | Planner user              | Resources area is visible when rights allow it    |
| RES-004 | Check restricted access | User without rights       | Setup actions are blocked                         |

#### Resource categories and creation

| ID      | Scenario                            | Test data    | Expected result                                                 |
| ------- | ----------------------------------- | ------------ | --------------------------------------------------------------- |
| RES-010 | Create a category                   | Vehicles     | Category is saved                                               |
| RES-011 | Create a resource with category     | RES-TRUCK-01 | Resource is saved as internal                                   |
| RES-012 | Create a resource without category  | RES-NOCAT-01 | Resource is saved but not plannable in category-based views     |
| RES-013 | Edit a resource                     | RES-TRUCK-01 | Updated values are saved                                        |
| RES-014 | Delete or archive a category in use | Vehicles     | Linked resource loses the category or is blocked by setup rules |

#### Scheduler and planning

| ID      | Scenario                                  | Test data                              | Expected result                                                     |
| ------- | ----------------------------------------- | -------------------------------------- | ------------------------------------------------------------------- |
| RES-020 | Show categorized resource in Scheduler    | RES-TRUCK-01                           | Resource appears under the assigned category                        |
| RES-021 | Check uncategorized resource in Scheduler | RES-NOCAT-01                           | Resource does not appear in category-based Scheduler view           |
| RES-022 | Link resource to work order               | WO-RES-001 + RES-TRUCK-01              | Work order shows the linked resource                                |
| RES-023 | Check overlapping planning visibility     | WO-RES-001 + WO-RES-002 + RES-TRUCK-01 | Existing allocation is visible to planners                          |
| RES-024 | Use spotlight for linked resource         | WO-RES-001 + RES-TRUCK-01              | Spotlight filters the view to the selected work and linked resource |
| RES-025 | Check standard browsing behavior          | Planner user A + Planner user B        | New resource changes may need a manual refresh to appear            |
| RES-026 | Check auto refresh while browsing         | Planner user A + Planner user B        | New resource changes appear after moving to another date or view    |

#### Work orders and mobile flow

| ID      | Scenario                                 | Test data                 | Expected result                                     |
| ------- | ---------------------------------------- | ------------------------- | --------------------------------------------------- |
| RES-030 | Add resource on work order in BackOffice | WO-RES-001 + RES-DRILL-01 | Resource link is saved                              |
| RES-031 | Remove resource from work order          | WO-RES-001 + RES-DRILL-01 | Resource link is removed                            |
| RES-032 | Add resource on mobile                   | Field user + WO-RES-001   | Resource can be selected if mobile flow supports it |
| RES-033 | Reopen saved work order                  | WO-RES-001                | Linked resources remain visible                     |

#### Tariffs and billing

| ID      | Scenario                             | Test data                    | Expected result                                   |
| ------- | ------------------------------------ | ---------------------------- | ------------------------------------------------- |
| RES-040 | Set tariffs on a resource            | RES-CRANE-01 + tariff values | Tariff values are saved                           |
| RES-041 | Link billable resource to work order | WO-RES-003 + RES-CRANE-01    | Work order accepts resource usage input           |
| RES-042 | Enter hourly usage                   | 2 hours                      | Price reflects the configured hour tariff         |
| RES-043 | Enter daily usage                    | 1 day                        | Price reflects the configured day tariff          |
| RES-044 | Leave tariffs empty                  | RES-DRILL-01                 | Resource remains plannable without billing values |

#### Regression checks

| ID      | Scenario                                                  | Test data                  | Expected result                                |
| ------- | --------------------------------------------------------- | -------------------------- | ---------------------------------------------- |
| RES-050 | Open existing resources after activation change           | Existing resources         | Data remains available after feature re-enable |
| RES-051 | Check Scheduler after category rename                     | Vehicles renamed           | Resource stays linked to the renamed category  |
| RES-052 | Check work order history after resource edits             | Existing linked work order | Historical links remain intact                 |
| RES-053 | Check Resources navigation after upgrade or add-on change | Eligible account           | Navigation and access remain correct           |

### Suggested execution order

1. Run activation tests.
2. Run category and creation tests.
3. Run Scheduler and work order tests.
4. Run tariff tests.
5. Finish with regression checks.

### Exit criteria

Use these criteria to close the test run:

* all critical tests pass
* no blocker remains open
* expected links between resources and work orders are correct
* Scheduler visibility matches category setup
* tariff calculations match the configured values

### Related topics

* [**Resources**](/marketplace-packages-and-power-ups/power-ups/resources.md)
* [**Create and manage resources**](/marketplace-packages-and-power-ups/power-ups/object-management/create-and-manage-resources.md)
* [**Use resources in the Scheduler**](/marketplace-packages-and-power-ups/power-ups/object-management/create-and-manage-resources/use-resources-in-the-scheduler.md)
* [**Features in Resources**](/marketplace-packages-and-power-ups/power-ups/resources/features-in-resources.md)
* [**Resources availability and plans**](/marketplace-packages-and-power-ups/power-ups/resources/resources-availability-and-plans.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/resources/test-plan-for-resources.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.