Sumo/Kitsune Dev Badge Testing 2018: Difference between revisions
< Sumo
Jump to navigation
Jump to search
(→Roland Win 10 desktop, FF62.0.3 testing: caching) |
(→Badges: testing for 17 october 2018) |
||
| Line 4: | Line 4: | ||
== Badges== | == Badges== | ||
=== 17 October 2018=== | |||
==== Roland Win 10 desktop, FF62.0.3 testing ==== | |||
* replaced a badge image and it worked! | |||
* verified profile was ok | |||
* added a new badge | |||
=== 4 October 2018=== | === 4 October 2018=== | ||
Revision as of 16:14, 17 October 2018
there will be further updates and testing when this is moved from dev to the staging server
Badges
17 October 2018
Roland Win 10 desktop, FF62.0.3 testing
- replaced a badge image and it worked!
- verified profile was ok
- added a new badge
4 October 2018
Roland Win 10 desktop, FF62.0.3 testing
- create a badge in /admin -
- upload a badge image - FAIL
- old image is not replaced by new image, might be a general dev server issue
- check profile for badges - PASS
- however some badge images are missing due to incomplete sync from production or staging?
- from https://dev.sumo.moz.works/en-US/user/rtanglao
- see: flic.kr/p/2bK6Sk8
- qualify for a badge and make sure badge is issued -
FAILPASS- created 10 edits and approved them but no 2018 kb badge issued at from: https://dev.sumo.moz.works/en-US/kb/firefox-reader-view-clutter-free-web-pages/history to me: https://dev.sumo.moz.works/en-US/user/rtanglao
- actually I see the badge at https://dev.sumo.moz.works/en-US/user/rtanglao now, I guess it takes an hour or two for the system to add the badge