---
title: "Unit Tests Priority & Complexity"
slug: "tests-and-recommended-unit-tests-priority-complexity"
updated: 2026-04-27T06:50:13Z
published: 2026-04-27T06:50:13Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://success.panaya.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Unit Tests Priority & Complexity

Depending on the type of project, the activity Priority and its corresponding Complexity are determined by the specific activity type. This article describes, per activity type, the meaning of the different priority and complexity levels.

| **Activity Type** | **Priority Level** | **Complexity Level** |
| --- | --- | --- |
| Recommended **Unit Test**Activities – **SPS/EHP** Upgrade (Generated by Panaya) | **High** If the transaction has associated code corrections (not including a problem in user exits) **Medium** Transaction is impacted directly by SAP notes **OR**calls an active user exit **AND No** associated code correction **Low** **No** associated code correction found, **and** the transaction is impacted indirectly by SAP notes **OR** Only an active User Exit code correction was found, **and**the User Exit is called by a transaction that is not impacted by SAP delivered notes. > [!WARNING] > **Note** If a Unit Test is only related to Authorization Adjustments, the priority will be set based on the highest related Authorization Adjustment priority | **Complex** If there are at least two code-correction predecessors **Medium** If there is exactly one code correction predecessor **Simple** No code correction predecessors |
| Recommended **Unit Test**Activities – **BW**, SPS/EHP Upgrade (Generated by Panaya) | **High** If the transaction has code corrections **Medium** No code correction problems, and the transaction is impacted directly by SAP notes | **Complex** More than 1 Code Correction **Simple** No code corrections, no notes, no Active User Exits **Medium** All the rest |
| Recommended **Unit Tests**Activities in **S/4Convert**Projects (Generated by Panaya) | **High** With at least one associated correction in high priority (Related Modifications are not considered) **Medium** - With at least one associated correction in low or medium priority. (Related Modifications are not considered) - No associated corrections, but the Transaction has active users exits **Low** Everything else | **Complex** More than 1 Code Correction **Medium** With Active User Exits, or with Related notes, or one related correction **Simple** All the rest |
| Recommended **Progression Tests**Activities in **S/4Convert** Projects (Generated by Panaya) | **For Transactions -** - **High** With at least one associated correction in high priority (Related Modifications are not considered) - **Medium** - With at least one associated correction in low or medium priority. (Related Modifications are not considered) - No associated corrections, but the Transaction has active user exits - **Low** Everything else **For Fiori** [](/v1/docs/tests-and-recommended-unit-tests-priority-complexity#recommended-progression-tests-activities-for-fioriaccording-to-replaced-transaction-usage-and-impact-level-as-in-the-below-table)[According to the replaced transaction usage and impact level](/v1/docs/tests-and-recommended-unit-tests-priority-complexity#progression-tests-for-fiori)[](/v1/docs/tests-and-recommended-unit-tests-priority-complexity#recommended-progression-tests-activities-for-fioriaccording-to-replaced-transaction-usage-and-impact-level-as-in-the-below-table) | **Complex** More than 1 Code Correction **Medium** With Active User Exits, or with Related notes, or one related correction **Simple** All the rest |
| Recommended **Unit Tests**Activities - **S/4Accelerate** Projects (Generated by Panaya) | **High** - Has predecessor tasks AND either - - Has transaction notes OR - Has APPC notes OR - Has non-user-exit custom code - The transaction has side effect notes - Role tasks exist with HIGH priority **Medium** - No predecessor tasks but has transaction notes - Has an active User Exit **Low** - No predecessor tasks and no transaction notes - Has only user exit custom code, no APPC notes, and no transaction notes |  |
| **Test**Activities in an **EHP/SPS**and **S/4Convert**projects (User Generated) | If Transactions are identified by Panaya and an associated Unit Test was generated with steps using these transactions, the Test priority is determined **according to the highest priority transaction correction** If the transaction is not specified - - **Low** - For all other Tests |  |
| **Test**Activities in a**Testing project** (User Generated) | **High** |  |

### **Progression Tests**for Fiori

According to the replaced transaction usage and impact level, as in the table below.

| **Impact Level / Usage** | **Frequently** | **Normally** | **Rarely** | **Unused** | **Unknown** |
| --- | --- | --- | --- | --- | --- |
| **Deleted** | High | High | Medium | - | - |
| **Obsolete** | High | Medium | Low | - | - |
| **Enhanced by Fiori** | Medium | Low | Low | - | - |