Move build test to its own file and test more aspects of build#354
Move build test to its own file and test more aspects of build#354marksiemers wants to merge 9 commits into
Conversation
|
@amberframework/core-team - These tests will still fail. Based on our discussion of CSRF in the generated controller spec files, it sounds like a fix could go in that will make the tests pass. In order to get them to pass, there is an issue that needs to be resolved in It is fixed here: https://github.com/amberframework/amber-spec/pull/7 |
|
Another error has been uncovered. I'm going to comment some lines out, but this will be good to address for a next release (getting this integration test to pass with everything): The full trace is here: https://www.zerobin.net/?85f41ce66ae44756#jqdAoilihS2iB+bX7Kdx+poCoa6lIYc17XDKnr3nm+A= |
|
I think this was fixed here. Need to release granite-orm |
|
It seems this integration test will be good at catching bugs introduced by dependencies and/or breaking changes. |
|
You'll see that I gutted a lot of what is being tested: 21b1083 If issues are resolved (like @drujensen mentioned), then some of these can be added back in. The thing that needs to be fixed is the @drujensen A couple questions:
|
|
@marksiemers yeah, i will release it tonight when i get a chance |
|
I can release if that's okay with you @drujensen |
|
Please do. I’m swamped. |
|
I released Granite 0.7.6. This should fix the issue with |
* Update dependencies * Remove branch comment * Fix shard build * Use test app name instead of path * More explicit build command to see failures * Downgrade mosop/cli * Try previous version of kilt
|
@amberframework/core-team - It looks like the change to amber-spec may have an issue. The error in this test is |
…s/amber into conditional-spec-builds-342-a
|
If #381 goes in, this can likely be closed, it includes these changes plus more. |
|
Done in #381 |
See #348
A big refactor of the specs was done before merging #348 - It was easier to just redo these changes.