Skip to content

build: test material with bazel #13670

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

Merged
merged 3 commits into from
Oct 24, 2018

Conversation

devversion
Copy link
Member

  • Supports testing src/lib with Bazel.

Note: Very few tests had to be updated because w/ Bazel the HTML files are not minified and therefore there could be some whitespace (even with preserveWhitespace = false by default).

@devversion devversion added pr: merge safe target: major This PR is targeted for the next major release labels Oct 18, 2018
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 18, 2018
@devversion devversion force-pushed the build/test-lib-with-bazel branch from f6bc578 to c5bf364 Compare October 18, 2018 19:29
@devversion devversion added target: patch This PR is targeted for the next patch release and removed target: major This PR is targeted for the next major release labels Oct 19, 2018
@josephperrott josephperrott removed their request for review October 22, 2018 17:14
@devversion devversion force-pushed the build/test-lib-with-bazel branch from c5bf364 to 0c2fa8c Compare October 22, 2018 17:42
@@ -72,15 +72,22 @@ def ng_test_library(deps = [], tsconfig = None, **kwargs):
**kwargs
)

def ng_web_test_suite(deps = [], srcs = [], static_css = [], **kwargs):
def ng_web_test_suite(deps = [], srcs = [], static_css = [], prebuilt_theme = False,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I wasn't clear in out conversation- the prebuilt_theme attribute should just be removed completely.

Copy link
Member Author

@devversion devversion Oct 22, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So just manually specify the theme for each target?

We cannot always add a theme if this macro is being used because the CDK tests also use the same macro.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking that it would be fine to include it for the cdk tests too; they shouldn't be affected either way.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, it's still feels a bit odd to have CDK tests use a prebuilt theme, but I agree that this makes it consistent to how the tests run w/ Gulp + themes shouldn't affect the CDK tests.

Done! please have another look 😄

@devversion devversion force-pushed the build/test-lib-with-bazel branch from 0c2fa8c to 1d9c58f Compare October 24, 2018 14:51
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Oct 24, 2018
@mmalerba mmalerba merged commit bec5823 into angular:master Oct 24, 2018
mmalerba pushed a commit that referenced this pull request Oct 26, 2018
* build: test material with bazel

* Supports testing `src/lib` with Bazel.

* Add prebuilt theme to all Material tests

* Always include prebuilt theme. Rebase changes for paginator spec
atscott pushed a commit to atscott/components that referenced this pull request Nov 5, 2018
* build: test material with bazel

* Supports testing `src/lib` with Bazel.

* Add prebuilt theme to all Material tests

* Always include prebuilt theme. Rebase changes for paginator spec
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants