Join our Multi-Account Containers Research Study! 🚀

[bakulf]

Before submitting your pull request

• I agree to license my code under the MPL 2.0 license.
• I rebased my work on top of the main branch.
• I ran npm test and all tests passed.
• I added test coverages if relevant.

Description

#2802

We are running several research studies with Multi-Account Containers users to learn more about your experiences with the add-on. Interviewees who participate in this first study will receive a $75 Amazon e-giftcard or Paypal transfer in appreciation for their time -- if you’d like to participate, please fill out the research interest form here! Thank you for helping us shape the future of Containers!

Type of change

• Bug fix
• New feature
• Major change (fix or feature that would cause existing functionality to work differently than in the current version)

[dannycolin]

I've tested with different values for containerTabsOpened (lower/higher than 10, hitting 100). Each tests worked as expected. When hitting 100, it showed the survey in priority and only showed the 100 tabs achievement the next time I opened the popup.

@bakulf Should we also account for the scenario where the survey deadline has ended or do you plan to clean up the achievement later on?

[bakulf]

@bakulf Should we also account for the scenario where the survey deadline has ended or do you plan to clean up the achievement later on?

We will ship a new version as soon as we have enough data from users.

[maxxcrawford]

Thanks for tagging me in the review!

[groovecoder]

Code and spot-check looks pretty good. Couple non-blocking question/suggestions.

[groovecoder]

@bakulf Should we also account for the scenario where the survey deadline has ended or do you plan to clean up the achievement later on?

We will ship a new version as soon as we have enough data from users.

Are you sure about that? IIRC, shipping a new version adds another QA cycle each time. Might be time-consuming just to remove the achievement.

[bakulf]

Are you sure about that? IIRC, shipping a new version adds another QA cycle each time. Might be time-consuming just to remove the achievement.

well, we will ship version 6.0 changing the version number. I suspect we do not need a deep QA exploration.