-
Notifications
You must be signed in to change notification settings - Fork 6
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
[MOB-2819] Removed 2nd tracking occurrance of onboarding page number #851
[MOB-2819] Removed 2nd tracking occurrance of onboarding page number #851
Conversation
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
PR Code Suggestions ✨Explore these optional code suggestions:
|
Just ran them locally and they passed, they are also ran on every PR with CI and your PR here looks good :) I remember seeing some flakiness on those tests, which one was it? I think the menu ones sometimes fail 🤔 |
Okay, thanks for having a look :) |
@@ -225,7 +225,6 @@ open class Analytics { | |||
let event = Structured(category: Category.intro.rawValue, | |||
action: Action.display.rawValue) | |||
.property(page.rawValue) | |||
.value(.init(integerLiteral: index)) |
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.
Can you also remove the index
(at index: Int
) from the function parameters since it's no longer needed?
I think that will also break the tests, so will require some refactoring there, but should be a nice learning opportunity 🙂
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.
Sure, I'll do that 👍
6ec081e
to
0bbef71
Compare
@lucaschifino Hey I just rebased and ran test again before wanting to address what you mentioned above. But like last week I can't successfully run our tests at the moment. It fails here: ![]() |
@TimNowaczynski just checked out your branch and If it still happens we can try to to debug better, is there a specific test case where this fails? Does it work if you run it on the simulator outside of the tests? |
Thanks, I'll check tomorrow 🤞 |
@lucaschifino After running those steps you mentioned the tests failed again, then after re-running everything a 2nd time things went fine. So for me they seem to be flaky for some reason. But that's fine for me now, looks like I didn't break anything. I'll now rebase things and then I'm done I guess. |
@TimNowaczynski Makes sense! There's indeed some flakyness on Analytics tests, trying to run it a couple times is a good idea until we tackle that, hope it isn't too much of a problem 🙈 I think the one other thing missing would be this other comment I left a while ago, not sure if you were able to check it out already 🙂 |
0bbef71
to
8b1214e
Compare
WIP: remove tracking invocations
@lucaschifino I'm pretty sure I removed too much now because tests fail for me in the |
Fixed line which should not have been removed
@lucaschifino Sorry for pinging you again, but I found it 😓 :) |
No worries! I believe Edit: Btw, noticed on CI here on the PR some flaky tests were also failing, re-ran it a couple times to try and get it green. |
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.
Looks great, thanks for the adjustments 👏
There's one last minor comment from my side.
Removed unused code fragment
@lucaschifino Thanks! Should be all right now :) |
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.
LGTM! Nice work 🎉 👏
The only thing missing is the CI being green, I just re-ran it as it failed again on the flaky test 🤞
https://ecosia.atlassian.net/browse/MOB-2819
My cat kinda deleted the PR Preset, but basically I removed two lines of code which seem to track the property in question.
I also ran tests and they actually failed in (and only in)
AnalyticsSpyTest.swift
but this seems to be already the case on the base banch. But before I mess something up, can you maybe look into that as well? Just to be safe :)