-
Notifications
You must be signed in to change notification settings - Fork 32
CV3-68 Refactor fixtures folder #515
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
base: develop
Are you sure you want to change the base?
Conversation
e2ee280
to
d9c3d84
Compare
e225efe
to
a3934ae
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work on the PR @adafia. Please take note of a few changes I've requested for. I have tried to make it precise and to the point.
010ecb1
to
8dbefb1
Compare
8dbefb1
to
88d3934
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good Work on the PR @adafia.
88d3934
to
972e057
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work @adafia
833576f
to
b969e9d
Compare
- split fixture files in question to query and response - add output builder to dynamically build fixture outputs [Finishes CV3-68]
b969e9d
to
82e42b7
Compare
Description
Some fixtures files have more than 250 lines which is flagged by code climate as bad practice. Reorganise the fixture files by breaking big files into smaller ones.
Type of change
Please select the relevant option
How Has This Been Tested?
How to Test
codeclimate
report to see if any file from the fixtures folder violates thefile-line-limit
readme.md
file on running tests. Check to see if tests run successfullyChecklist
JIRA
CV3-68