-
Notifications
You must be signed in to change notification settings - Fork 132
Standalone has issues validating tests in 2.3.0-beta32 #278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @lazyguru |
@okolesnyk I see that the internal ticket you mention (https://jira.corp.magento.com/browse/MQE-1367) is CLOSED as DONE. It's not immediately clear to me how that issue solves this problem, but if you feel that it does then please close this github issue or I will close it by the end of the week. Thanks! |
@lazyguru I'm trying to find out if the issue you reported still occurs. Could you verify that with latest MFTF version and share the update? I'm asking because if the failure still occurs, I can address that next weekend. |
I'm not sure. We don't try running via standalone anymore and just use the built-in version of MFTF. |
@lazyguru If you still have problems, please create a new ticket. |
Merging master back to develop
Uh oh!
There was an error while loading. Please reload this page.
I am trying to build our own suite to run tests. I am testing using MFTF standalone per the directions here https://devdocs.magento.com/mftf/2.3/getting-started.html#set-up-a-standalone-mftf. When I try to generate a single test or our suite, I get errors from other (unrelated) tests.
See Slack thread for more info: https://magentocommeng.slack.com/archives/C82DDUSNP/p1542748941043300
Preconditions
Steps to reproduce
bin/mftf generate:suite MySuite
orbin/mftf generate:test MySingleTest
Expected result
Actual result
The following files all fail validation for different reasons. I only captured the actual errors from the first one. I manually deleted the files at each run to try to get the generation of just our suite to run. I also ran the generation with the debug flag (-d) to get this output
The text was updated successfully, but these errors were encountered: