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

Redesign the config file #50

Merged
merged 1 commit into from
Oct 23, 2018

Conversation

zhongyi-zhang
Copy link
Collaborator

@zhongyi-zhang zhongyi-zhang commented Oct 15, 2018

Solve #48.
Also do a refactor on the test framework.

This PR tries to do a minimal change on the test framework to adjust the config redesign. All the test cases are kept. Something that not looks good to me are just commented as TODO.
Currently only the mock server can be ensured to pass all the test cases. Will create subsequent issues and PRs to continue improving the checker.

The change in test.js is huge. Git diff works not very well on it. Actually most of the original logic are kept. The refactor only optimizes how to trigger them according to the new config file. Appreciate your reviews!

@cfdreddbot
Copy link

Hey zhongyi-zhang!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.

"organization_id":"org-guid-here",
"space_id":"spcae-guid-here"
{
"operation": "deprovision",
Copy link
Collaborator

Choose a reason for hiding this comment

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

According to the spec, I'm wondering if it's better to add plan_id field here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Let me clarify that, the config file no longer directly specifies the request body. The test framework is able to what the plan_id is currently and build the request body.

"platform": "cloudfoundry",
"some_field": "some-contextual-data"
{
"operation": "bind",
Copy link
Collaborator

@leonwanghui leonwanghui Oct 16, 2018

Choose a reason for hiding this comment

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

Doesn't it need some optional fields such like context and bind_resource?

Copy link
Collaborator Author

@zhongyi-zhang zhongyi-zhang Oct 16, 2018

Choose a reason for hiding this comment

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

The field is optional and the test framework doesn't add any case for it. So, I refine this in the new config file. Anytime we can add it back for new cases which require it. Does it make sense?

Copy link
Collaborator

@norshtein norshtein left a comment

Choose a reason for hiding this comment

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

Haven't gone deeply into single test cases. The refactoring of the framework LGTM.

@leonwanghui
Copy link
Collaborator

I think the framework is generally ok, and I noticed there are several TODO items which are related to some other PRs, so I will rebase my PRs after this PR merged.

@zhongyi-zhang
Copy link
Collaborator Author

zhongyi-zhang commented Oct 19, 2018

@leonwanghui thanks for the review. Looking forward to the PRs after rebase. I'll help review.
@duglin @fmui @kibbles-n-bytes hi, it seems that the Pull Approve requires at least 2 of your approvals in the list. I'd like to respect the PR merging process. Could you help? Thanks!

@duglin
Copy link
Contributor

duglin commented Oct 19, 2018

LGTM

Approved with PullApprove

@zhongyi-zhang
Copy link
Collaborator Author

zhongyi-zhang commented Oct 22, 2018

Thanks! Now one more approval is required... @mattmcneeney as you know about the redesign, could you approve it? BTW, can @norshtein, @leonwanghui, and me be added to the .pullapprove.yml? It would help the project move faster on the non-critical PRs (e.g. fixing typo) and engineering-only PRs (e.g. fixing logic which is not reflecting the purpose of a case) -- what we are pretty sure that they can be merged.

@mattmcneeney
Copy link
Contributor

@zhongyi-zhang I have added @norshtein and @leonwanghui as approvers. Thanks and have fun!

@mattmcneeney
Copy link
Contributor

@zhongyi-zhang I have added @norshtein and @leonwanghui as approvers. Thanks and have fun!

4 similar comments
@mattmcneeney
Copy link
Contributor

@zhongyi-zhang I have added @norshtein and @leonwanghui as approvers. Thanks and have fun!

@mattmcneeney
Copy link
Contributor

@zhongyi-zhang I have added @norshtein and @leonwanghui as approvers. Thanks and have fun!

@mattmcneeney
Copy link
Contributor

@zhongyi-zhang I have added @norshtein and @leonwanghui as approvers. Thanks and have fun!

@mattmcneeney
Copy link
Contributor

@zhongyi-zhang I have added @norshtein and @leonwanghui as approvers. Thanks and have fun!

@mattmcneeney mattmcneeney reopened this Oct 22, 2018
@norshtein
Copy link
Collaborator

norshtein commented Oct 22, 2018

LGTM

Approved with PullApprove

@cfdreddbot
Copy link

Hey zhongyi-zhang!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.

Copy link
Collaborator

@leonwanghui leonwanghui left a comment

Choose a reason for hiding this comment

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

LGTM

@zhongyi-zhang zhongyi-zhang merged commit bd395e0 into openservicebrokerapi:master Oct 23, 2018
@zhongyi-zhang
Copy link
Collaborator Author

@mattmcneeney thanks!! Seems the change doesn't have an effect on the existing PR... Just merge it this time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants