nicolasritouet/fullstacktesting-frontend

Fullstacktesting - Frontend

The purpose of this project is to collaborate on best practices with modern test tools.

This example is based on a frontend (built with angular2) and a backend (built with koa2). Docker and docker-compose are used to bootstrap the environment and test with all different components. Some tools we use:

• docker-selenium
• postgresql

This project was generated with angular-cli version 1.0.0-beta.19-3.

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.

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. Before running the tests make sure you are serving the app via ng serve.

Deploying to Github Pages

Run ng github-pages:deploy to deploy to Github Pages.

Further help

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

fullstacktesting-frontend's Issues

An in-range update of karma-remap-istanbul is breaking the build 🚨

Version 0.2.2 of karma-remap-istanbul just got published.

Branch	Build failing 🚨
Dependency	karma-remap-istanbul
Current Version	0.2.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As karma-remap-istanbul is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 4 commits .

• 5fc07af 0.2.2
• 9dfa5f1 Add webpack e2e example (#22)
• aec4fba Merge pull request #27 from mateuszjuszkiewicz/issue-21-unable-to-find-entry
• c67d9b0 Do not pass empty sourceStore into writeReport

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of @angular/forms is breaking the build 🚨

Version 2.2.2 of @angular/forms just got published.

Branch	Build failing 🚨
Dependency	@angular/forms
Current Version	2.2.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As @angular/forms is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

Version 6.0.47 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	6.0.46
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of typescript is breaking the build 🚨

Version 2.0.7 of typescript just got published.

Branch	Build failing 🚨
Dependency	typescript
Current Version	2.0.6
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As typescript is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

TypeScript 2.0.7

This release includes a targeted fix for declaration file acquisition to use a local copy of types-registry to find @types packages instead of querying npm.

Download:

• npm

Commits

The new version differs by 5 commits .

• dbf69b7 Update LKG
• 17735cd Update version
• 1b9acca use local registry to check if typings package exist (#12014)
• 4c67000 Merge pull request #11869 from Microsoft/vladima/11852
• 6041fce support both old and new set of settings in the formatting API

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of @types/jasmine is breaking the build 🚨

Version 2.5.38 of @types/jasmine just got published.

Branch	Build failing 🚨
Dependency	@types/jasmine
Current Version	2.5.37
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/jasmine is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of zone.js is breaking the build 🚨

Version 0.6.26 of zone.js just got published.

Branch	Build failing 🚨
Dependency	zone.js
Current Version	0.6.25
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As zone.js is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 15 commits .

• 21935e8 chore: bump npm version to 0.6.26
• 431f6f0 fix(node): crash when calling listeners() for event with no listeners
• abaac6f test(setTimeout): use explicit timeout delays where order matters
• fea6d68 fix: support clearing the timeouts with numeric IDs
• 63bca67 refactor: add copyright header to source files
• 0bc6035 style: format ts files
• 3ffc664 build: add a clang-format task
• ed87c26 fix: lint errors
• 2cad6b3 build: add a gulp lint task
• 16be7f9 fix: make fetch promise patching safe
• a85db4c fix: run all timers in passage of time in a single fakeAsync's tick call
• b52cf02 fix: stop using class extends as it breaks rollup
• 7da0c52 fix(safari) - webworker objects have no .hasOwnProperty method, use
• 51f2e1f fix(property-descriptor): do not use document object in Safari web worker
• 737f8d8 fix(promise): include stack trace in an unhandlerd promise (#463)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴