Marco Bonardo [:mak] Reporter
	Description • 9 years ago

Before enabling transactions we should do a round of manual testing of the most common operations with browser.places.useAsyncTransactions set to true:

create a bookmark
change something of it
remove a bookmark
copy&paste a bookmark
cut&paste a bookmark
drag&drop a bookmark

Do the same for folders and separators and livemarks

Do the same for a folder with some hierarchy inside

Test drag&drop of queries (like tag containers) and dropping inside a tag container in the library.

for each operation, we can also try to undo it through the Library

We could probably ask someone from QE, since we don't have developers time to share atm :/

This might happen after bug 1095425 is resolved.

	Marco Bonardo [:mak] Reporter
	Comment 1 • 7 years ago

Brindusa, we will need QA coverage for Async Places Transactions.

This code is behind most of the operations regarding bookmarks in the UI (creation, editing, moving, removal), included the star button. Potentially anything you can do with bookmarks in the ui goes through this layer.
We should create a test plan and check the status of the feature, that is currently enabled only in Nightly (from today's build I think since it was merged 13 hours ago), and we'd like to let it ride the train to release in v57.
The pref controlling the behavior is browser.places.useAsyncTransactions
I'm available to share any useful information.

	Brindusa Tot, Desktop QA
	Comment 2 • 7 years ago

Hi Mak,

Could you please also send a PI testing request to this alias: pi-request@mozilla.com, with a few details. We’ve been starting using this alias for the Product Integrity group for some time now and trying to gather here all testing & security requests. We’ve implemented this process for a better visibility of all QA work that needs to be done and this alias is being monitored daily by a large number of people from the PI group. 

What should a PI request contain:
- Project Name
- Work description
- Timeline
- Priority

Please feel free to use this alias for all testing requests from now on.

Thank you!

	Marco Bonardo [:mak] Reporter
	Comment 3 • 7 years ago

Sent the e-mail, QE will be done by Hani Yacoub

	Marco Bonardo [:mak] Reporter
	Comment 4 • 7 years ago

Brindusa, we plan to finally release this in 58, we are ready for testing as soon as bug 1392533 is in Nightly.
We are quite happy with the status of automated testing and had a call-to-action for volunteers testing, but having any QE support would be appreciated regardless.

Not sure if this bug is useful, apart for communicating.

	Brindusa Tot, Desktop QA
	Comment 5 • 7 years ago

Hi Mak,

As previously said, please send a PI testing request to the pi-request@mozilla.com alias with same details. Please keep in mind that for Fx 58, features have been prioritized, therefore please take a look at the prioritized list: https://goo.gl/WZRqwP, and let us know, where this feature would fit in.

Thank you!

	Marco Bonardo [:mak] Reporter
	Comment 6 • 7 years ago

I just sent a new email to Product Integrity.
I don't think we need this bug for anything in particular, regressions and eventual QE bugs can (and should) be filed apart and we'll prioritize and track them in the team's backlog.
I think the scope of this bug expired with the intent to ship mail.