search

actmd / abraham

Trackable application tours for Rails with i18n support
MIT License
124 stars 45 forks source link

Reports of tours not being displayed in production - how to debug ? #9

Closed kofronpi closed 5 years ago

kofronpi commented 7 years ago

I have reports of a tour not being displayed in production on different environments, for new users who never saw it.

I find it hard to track the reason - did you guys ever experiment that ?

I see it correctly with my own account.

jabbett commented 7 years ago

I will try to prioritize adding a browser-based test with Spinach and Capybara so we can automate testing on different environments. Do you have any suspicions? What browsers does your app try to support?

On Fri, Feb 17, 2017 at 5:58 AM, Pierre-Alexandre Kofron < notifications@github.com> wrote:

I have reports of a tour not being displayed in production on different environments, for new users who never saw it.

I find it hard to track the reason - did you guys ever experiment that ?

I see it correctly with my own account.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/actmd/abraham/issues/9, or mute the thread https://github.com/notifications/unsubscribe-auth/AA4ZQ12bDuH2eANQDJYMLE-9_b01vcbRks5rdX1mgaJpZM4MEIu5 .

--

Jonathan Abbett VP of User Experience ACT.md http://act.md/ | 401 Park Drive, Suite 814 · Boston, MA 02215

Act together. Make health happen.

kofronpi commented 7 years ago

Chrome, Firefox, Edge, Opera mainly. It happened on Chrome even after emptying the cache/cookies. I will investigate further

jabbett commented 5 years ago

Hi @kofronpi!

Given abraham's v2 release, I wanted to circle back on this ticket. The project now has browser-based system tests, and they get run automatically across Rails versions with Travis CI. Since your question, we also improved how abraham creates and manages its "show later" cookie.

So, overall, the gem should be more reliable now.

I have also added #25 to test for potential cross-browser issues.

Feel free to reopen the ticket if I can help further!