Skip to content
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

HSC-1124 - Mock Server to mock number of connected HCF endpoints and available applications #727

Merged
merged 17 commits into from
Oct 4, 2016

Conversation

irfanhabib
Copy link
Contributor

The mock-server currently does the following:

  1. Allows the user to configure a specific number of connected endpoints.
  2. Number of apps available on each endpoint can be randomly configured between a min/max value or endpoints can have a fixed number of apps.
  3. Requires a portal-proxy configured with an HCF. It proxies requests the service doesn't mock to the portal-proxy. These include: authentication requests, stats request (in case the ID of a running application has been specified).

@irfanhabib
Copy link
Contributor Author

@nwmac Can you test this?

@irfanhabib irfanhabib changed the title HSC-1124 - Mock Server to mock connected of HCF endpoints and available applications HSC-1124 - Mock Server to mock number of connected HCF endpoints and available applications Sep 29, 2016
@sean-sq-chen
Copy link
Contributor

Code looks great! One minor thing, we have been using a convention that having a mock file for x.js using the name x.mock.js and put it in the same folder as x.js. It is possible to follow the convention for this PR?

@nwmac
Copy link
Contributor

nwmac commented Oct 4, 2016

I guess this is a different kind of mock to the .mock files - we should think about naming and folder location for this.

@nwmac nwmac merged commit cb5dbd9 into master Oct 4, 2016
@nwmac nwmac deleted the 1124-mock-for-pagination branch October 4, 2016 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants