-
Notifications
You must be signed in to change notification settings - Fork 192
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
Fix #3250 - Makes form wizard the default #3252
Conversation
This test
and this test
Let's see if we can fix those two. |
ok fixed one test… maybe. circleci will tell us if we are off. |
Fixing the test will be painful. It dies silently node ./tests/functional/_intern.js "--functionalSuites=tests/functional/reporting-non-auth.js" |
🤔 puzzling
what do i do wrong? |
I wish i could run leadfoot inside the browser console. |
oh wait the new form is already tested in |
ok this is more logical all tests are failing for the wizard form. so that means that the files are being cached.
|
I exhausted github through circleci for a little while. Let's wait. |
I've checked out the branch, looks like it's not working because this condition is still in the templates (layout.html, new-issue.html):
|
Also this should be removed? Probably no point of adding the label if all reports will be going through the new form webcompat.com/webcompat/helpers.py Lines 763 to 768 in fdf8bef
|
|
ok this is much better now that I have fixed my issue with #3255 and a couple of other things. |
These are the tests failing
|
Our AB testing experiment is finished. We could remove all this code or just make it more abstract for the next experiment we would want to do. So in this commit I removed the mention of form.
I'm not sure this test is fully neede or at least not in this form. There might be room for a more generic tests related to if there is an AB experiment going on and we choose to add a label, how do we track and test this.
some tests have been removed because duplicated elsewhere. some partially rewritten. The new form is definitely more challending to test than the previous one and there is a lot of repeat. In fact I would probably see in the future a way where we can branch scenarios in the tests through meta function, instead of repeating the same code again and again.
Instead of keeping the choice in between the old form and the wizard form, we make the wizard form the default. we should create another issue to finally remove all the code related to the old form.
@ksy36 This is request for another review. the code changed quite a bit and i modified things with your recommendations. @miketaylr I decided to make the wizard form the default. also each commit as an extended description explaining the line of thoughts. |
@@ -226,25 +225,23 @@ def get_variation(variation_key, variations_dict, defaults_dict): | |||
|
|||
# Get AB experiment variation values from the environement. | |||
AB_VARIATIONS = { | |||
'FORM_V1_VARIATION': os.environ.get('FORM_V1_VARIATION', '0 100'), | |||
'FORM_V2_VARIATION': os.environ.get('FORM_V2_VARIATION', '100 100'), | |||
'V1_VARIATION': os.environ.get('V1_VARIATION', '0 100'), |
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.
@karlcow can you make sure to update the environment variables on the server to match this?
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.
(i did this)
I think we're good to merge and deploy (to staging first). |
This PR fixes issue #3250
Proposed PR background
My feeling is that if we are out of the experimental phase, we probably need to just not go through the AB code at all, and all of it becomes a lot simpler.
We can keep in place the code for future AB experiments and open a new issue for removing the old form code and tests once @ksy36 has finished refactoring the rest of the code for the new form.
So on this hypothesis, let's create a new PR. I expect tests to break badly. That's an Achilles' heel of our current setup. The AB experiment was an experiment at the beginning. Never let an experiment grows without the proper setup. We need to fix it.
Unit testing seems to work. There was a simple fix. The big breakage should happen on the functional tests side. Let's create a PR and see how much CircleCI is not happy about it.