Testing phase for v1.3 (beta 5)
See original GitHub issueHello there,
anyone who’s up for a bit of testing in order to get an earlier glimpse at the new features of the upcoming floccus version can follow the guide below:
Chrome
- Download the build here: https://github.com/marcelklehr/floccus/releases/tag/v1.3.0-beta.5
- Unzip the zip file
- In chrome go to
chrome://extensions/
- Enable developer mode
- Click
Load unpacked extension
and select the root folder of the floccus build
Firefox
- Download the build here: https://github.com/marcelklehr/floccus/releases/tag/v1.3.0-beta.5
- Unzip the zip file
- In firefox go to
about:debugging
- Click
Load tempoprary addon
and select the manifest file in the root folder of the floccus build
Upgrading
- Floccus will not recognize any previously setup bookmarks account, so you’ll need to create a new one and click
force Sync
after the account has been validated (Don’t copy over your old bookmarks from the old floccus folder, but let it fetch them from the server).
Debugging
In order to aid in debugging, please provide client-side logs.
Firefox
- Go to
about:debugging
- click on
debug
button next to floccus entry - go to floccus options and make sure the account of your choice is connected
- trigger a sync by clicking on
force Sync
for the account of your choice. - go back to the inspector window and copy the logs after waiting approx. 2mins
- paste the logs somewhere else removing any sensbile info and link to the site here (e.g. use https://pastebin.com)
Chrome
- Go to
chrome://extensions
- enable
Developer mode
- click on
dist/html/background.html
button in floccus’ entry next to "Inspect views: " - go to floccus options and make sure the account of your choice is connected
- trigger a sync by clicking on
force Sync
for the account of your choice - go back to the inspector window and copy the logs after waiting approx. 2mins
- paste the logs somewhere else removing any sensbile info and link to the site here (e.g. use https://pastebin.com)
Cheers! Marcel
Issue Analytics
- State:
- Created 6 years ago
- Comments:23 (13 by maintainers)
Top Results From Across the Web
Beta Testing: 6 Steps for a Successful Beta Testing Phase
1. Complete alpha testing. Alpha testing should resolve any and all known issues or bugs prior to the beta phase. · 2. Decide...
Read more >What is Beta Testing? A Complete Guide
Beta Testing is a customer validation methodology which allows the ... #3) Product Launch; #4) Collect and Evaluate Feedback; #5) Closure.
Read more >Software release life cycle - Wikipedia
The beta phase generally begins when the software is deemed feature complete, yet likely to contain several known or unknown bugs.
Read more >Alpha and Beta Testing - FFXIV Info
Phase 3 begins 1-2 weeks after phase 1 ends and will last 1-3 weeks. The purpose of this test is for version 1.0...
Read more >macOS 13 Ventura beta 5 now available to developers
macOS 13 Ventura beta 5 is finally available to developers. Apple is seeding a new build to developers to keep testing what's next...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
v1.3.0 is out. Have fun 😃
hey marcel, great job so far. so what about this guess of mine: why not releasing a new version of floccus just now where everything seems to be working fine? and then come up with a new version with said new features (i’d so love floccus&bookmarks to support folders!)? cheers jimmy