Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
angular/integration/forms
History
Paul Gschwendtner f51b00916e build: fix integration test size trackings not running after recent refactoring (#44430) 
Fixes that the integration test size trackings stopped working due to
the recent refactorings (switch to the rule from `@angular/dev-infra-private`).

The size-tracking does not integrate very-well into Bazel and needs
a better solution in the future, allowing for RBE and Windows support,
but currently with the new rule/setup/structure the tracking does not
validate sizes because:

* The `dist/*.js` argument to the tracking script got expanded and
  messed up the indices. It should be passed as a literal. This now
  surfaced because the new rule runs commands in a shell.

* The name for the size goldens were not computed properly because they
  were based on `ctx.attr.name`, but given the new structure, the test
  targets are always named `test`.

PR Close #44430
2021-12-10 16:31:04 -05:00
..
e2e test: switch integration tests from puppeteer/webdriver-manager to Bazel-managed chromium (#44238) 2021-12-08 13:42:42 -05:00
src test(forms): add integration test app to keep track of payload size (#41045) 2021-03-05 09:45:42 -08:00
.browserslistrc test: update browserslist configuration to replace Angular CLI projects (#43417) 2021-09-24 10:49:39 -07:00
.editorconfig test(forms): add integration test app to keep track of payload size (#41045) 2021-03-05 09:45:42 -08:00
.gitignore test(forms): add integration test app to keep track of payload size (#41045) 2021-03-05 09:45:42 -08:00
angular.json test: remove progress option from dev-server builder (#43730) 2021-10-06 09:23:59 -07:00
BUILD.bazel build: fix integration test size trackings not running after recent refactoring (#44430) 2021-12-10 16:31:04 -05:00
karma.conf.js test: switch integration tests from puppeteer/webdriver-manager to Bazel-managed chromium (#44238) 2021-12-08 13:42:42 -05:00
package.json test: switch integration tests from puppeteer/webdriver-manager to Bazel-managed chromium (#44238) 2021-12-08 13:42:42 -05:00
README.md test(forms): add integration test app to keep track of payload size (#41045) 2021-03-05 09:45:42 -08:00
tsconfig.app.json test(forms): add integration test app to keep track of payload size (#41045) 2021-03-05 09:45:42 -08:00
tsconfig.json test(forms): add integration test app to keep track of payload size (#41045) 2021-03-05 09:45:42 -08:00
tsconfig.spec.json test(forms): add integration test app to keep track of payload size (#41045) 2021-03-05 09:45:42 -08:00
tslint.json test(forms): add integration test app to keep track of payload size (#41045) 2021-03-05 09:45:42 -08:00
yarn.lock test: switch integration tests from puppeteer/webdriver-manager to Bazel-managed chromium (#44238) 2021-12-08 13:42:42 -05:00

README.md

Forms test app

This project was generated with Angular CLI.

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via Protractor.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.