Static composer tests fail on fresh install
If I clone a fresh copy of magento2 and run vendor/bin/phpunit -c dev/tests/static/phpunit.xml.dist, the ComposerTest fails because each packaged module has a 'version' property.
Version must not be specified in the root and package composer JSON files in Git
Failed asserting that object of class "stdClass" does not have attribute "version".
Am I missing something? I could mark the ComposerTest as skipped but it seems a bit messy. Does php bin/magento dev:tests:run static handle multiple composer files any better?
magento2
asked Dec 17 '18 at 16:58
strangerpixelstrangerpixel
1061
add a comment |
If I clone a fresh copy of magento2 and run vendor/bin/phpunit -c dev/tests/static/phpunit.xml.dist, the ComposerTest fails because each packaged module has a 'version' property.
Version must not be specified in the root and package composer JSON files in Git
Failed asserting that object of class "stdClass" does not have attribute "version".
Am I missing something? I could mark the ComposerTest as skipped but it seems a bit messy. Does php bin/magento dev:tests:run static handle multiple composer files any better?
magento2
asked Dec 17 '18 at 16:58
strangerpixelstrangerpixel
1061
add a comment |
If I clone a fresh copy of magento2 and run vendor/bin/phpunit -c dev/tests/static/phpunit.xml.dist, the ComposerTest fails because each packaged module has a 'version' property.
Version must not be specified in the root and package composer JSON files in Git
Failed asserting that object of class "stdClass" does not have attribute "version".
Am I missing something? I could mark the ComposerTest as skipped but it seems a bit messy. Does php bin/magento dev:tests:run static handle multiple composer files any better?
magento2
asked Dec 17 '18 at 16:58
strangerpixelstrangerpixel
1061
If I clone a fresh copy of magento2 and run vendor/bin/phpunit -c dev/tests/static/phpunit.xml.dist, the ComposerTest fails because each packaged module has a 'version' property.
Version must not be specified in the root and package composer JSON files in Git
Failed asserting that object of class "stdClass" does not have attribute "version".
Am I missing something? I could mark the ComposerTest as skipped but it seems a bit messy. Does php bin/magento dev:tests:run static handle multiple composer files any better?
magento2
magento2
asked Dec 17 '18 at 16:58
strangerpixelstrangerpixel
1061
asked Dec 17 '18 at 16:58
strangerpixelstrangerpixel
1061
asked Dec 17 '18 at 16:58
strangerpixelstrangerpixel
1061
asked Dec 17 '18 at 16:58
strangerpixelstrangerpixel
1061
asked Dec 17 '18 at 16:58
strangerpixelstrangerpixel
1061
1061
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It emerged that, on older branches of magento/magento2, Magento modules specify a version in their composer files, which results in the above error. However, on the latest 2.3-develop branch the composer files do not display a version and therefore pass the ComposerTest - so I'm testing against that going forward.
answered yesterday
strangerpixelstrangerpixel
1061
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f254931%2fstatic-composer-tests-fail-on-fresh-install%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It emerged that, on older branches of magento/magento2, Magento modules specify a version in their composer files, which results in the above error. However, on the latest 2.3-develop branch the composer files do not display a version and therefore pass the ComposerTest - so I'm testing against that going forward.
answered yesterday
strangerpixelstrangerpixel
1061
add a comment |
It emerged that, on older branches of magento/magento2, Magento modules specify a version in their composer files, which results in the above error. However, on the latest 2.3-develop branch the composer files do not display a version and therefore pass the ComposerTest - so I'm testing against that going forward.
answered yesterday
strangerpixelstrangerpixel
1061
add a comment |
It emerged that, on older branches of magento/magento2, Magento modules specify a version in their composer files, which results in the above error. However, on the latest 2.3-develop branch the composer files do not display a version and therefore pass the ComposerTest - so I'm testing against that going forward.
answered yesterday
strangerpixelstrangerpixel
1061
It emerged that, on older branches of magento/magento2, Magento modules specify a version in their composer files, which results in the above error. However, on the latest 2.3-develop branch the composer files do not display a version and therefore pass the ComposerTest - so I'm testing against that going forward.
answered yesterday
strangerpixelstrangerpixel
1061
answered yesterday
strangerpixelstrangerpixel
1061
answered yesterday
strangerpixelstrangerpixel
1061
answered yesterday
strangerpixelstrangerpixel
1061
1061
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f254931%2fstatic-composer-tests-fail-on-fresh-install%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
