|
| 1 | +# Testing Bugfender SDK for Unity |
| 2 | + |
| 3 | +This document describes the manual validation flow for the Unity SDK package. |
| 4 | + |
| 5 | +## Test project |
| 6 | + |
| 7 | +Use the sample project at: |
| 8 | + |
| 9 | +`/home/aleix/Projects/bugfender/unity-demo` |
| 10 | + |
| 11 | +To test local package changes, the sample project's package manifest should point to: |
| 12 | + |
| 13 | +`file:../../BugfenderSDK-Unity` |
| 14 | + |
| 15 | +## Unity version |
| 16 | + |
| 17 | +Validate with Unity `6000.3.10f` or the target Unity 6 version under support. |
| 18 | + |
| 19 | +## Import checks |
| 20 | + |
| 21 | +1. Open `/home/aleix/Projects/bugfender/unity-demo` in Unity. |
| 22 | +2. Wait for Package Manager and asset import to finish. |
| 23 | +3. Confirm the Bugfender package resolves from the local file path. |
| 24 | +4. Confirm there are no C# compilation errors. |
| 25 | +5. Confirm there are no Android plugin import errors for `Bugfender.androidlib`. |
| 26 | +6. Confirm there are no iOS plugin compilation issues for `BugfenderBridge.mm`. |
| 27 | + |
| 28 | +## Android build checks |
| 29 | + |
| 30 | +1. Switch the active platform to Android. |
| 31 | +2. Build the sample project. |
| 32 | +3. If the build fails, capture the first Gradle error block. |
| 33 | + |
| 34 | +Expected result: |
| 35 | + |
| 36 | +- No `Could not find com.bugfender.sdk:android` errors. |
| 37 | +- No `ClassNotFoundException` or `cannot find symbol` errors for `com.bugfender.sdk.Bugfender`. |
| 38 | +- No missing module or `Project with path` errors involving `Bugfender.androidlib`. |
| 39 | + |
| 40 | +## iOS build checks |
| 41 | + |
| 42 | +1. Switch the active platform to iOS. |
| 43 | +2. Build the Xcode project from Unity. |
| 44 | +3. Open the generated Xcode project and build it. |
| 45 | + |
| 46 | +Expected result: |
| 47 | + |
| 48 | +- Swift Package Manager resolves `BugfenderSDK-iOS`. |
| 49 | +- No compile or link errors for `Bugfender`. |
| 50 | +- No selector or symbol errors related to `setSDKType:version:`. |
| 51 | + |
| 52 | +## Runtime checks |
| 53 | + |
| 54 | +1. Set a valid Bugfender app key in the sample scene. |
| 55 | +2. Run the app on a device or simulator. |
| 56 | +3. Confirm startup completes without crashing. |
| 57 | +4. Confirm Bugfender initializes successfully. |
| 58 | +5. Send a test log and verify it appears in Bugfender. |
| 59 | + |
| 60 | +## What to capture on failure |
| 61 | + |
| 62 | +When reporting a failure, include: |
| 63 | + |
| 64 | +- Unity version |
| 65 | +- Target platform |
| 66 | +- Whether the failure happens during import, build, or runtime |
| 67 | +- The first relevant error block from Unity Console, Gradle, or Xcode |
0 commit comments