v3.3.0-beta.6 breaks my addon's test suite - something I'm doing wrong? #5497
-
I've been running into the same issue for the last few hours and can't figure out how to fix it... hopefully someone here can help: I run into this issue when running my addon's test suite on v3.3.0-beta.6 but not when on beta.5 (it passes fine). Seems related to it not being able to find blueprints for the entries. In my addon test suite, it should be using the blueprints in this folder, and pulling them in like so in the Blueprint::setDirectory(__DIR__ . '/../resources/blueprints'); I've tried renaming the blueprint files from One commit, everything was passing, the next, most tests were failing due to this issue. Here's an example of a run where I'm seeing the issues: https://github.com/doublethreedigital/simple-commerce/runs/5544587419?check_suite_focus=true How to reproduce
FYI: I created this as a discussion as I'm not sure it's really a bug, more than likely something is setup wrong on my side or needs adjusted to work with 3.3. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I noticed that one of your tests creates a Stuff changed on the master branch recently that happens when the files are initially read - you may have just been getting away with the wonky entry silently until now. |
Beta Was this translation helpful? Give feedback.
I noticed that one of your tests creates a
product
entry with ablueprint: orders
, which doesn't seem right.Stuff changed on the master branch recently that happens when the files are initially read - you may have just been getting away with the wonky entry silently until now.