Update seed testing instruction.

[goodov]

No description provided.

[github-actions]

✅ Test Seed Generated Successfully

To apply the test seed:

1. Desktop: Launch the browser with --variations-pr=1129.
   Android: Set the command line to --variations-pr=1129 in debug menu, restart the browser.
   iOS: Set Variations PR to 1129 in Brave Core Switches debug menu, restart the browser.
2. Wait 5-10 seconds to fetch the seed.
3. Restart the browser to apply the seed.
4. Ensure Active Variations section at brave://version starts with the expected seed version (see below).

Seed Details

• Version: pull/1129@2c553a195cab4a3cec670511411f9bc8bbdf9ecf
• Uploaded: 2024-07-19T06:16:44.578Z
• Serial Number: fd4febf939631858f63e85c905993215

[goodov]

cc @brave/qa-team

can you please proof-read the instruction about testing the seed and improve it if possible (see the comment in this pull request)? Maybe you have a better naming internally for "the debug menu" on android/ios respectively.

[stephendonner]

What's this about? Is it an intentional change, or a typo?

The rest looks good to me for desktop 👍

[goodov]

it's a test change to trigger the seed generation (I'm not going to commit it).

[kjozwiak]

LGTM other than the issue that @stephendonner pointed out re: Enabledd. Instructions should be good enough. At this point, most of QA should be able to figure out how to verify using the new method but I'll point them to our verifications via brave/brave-core#24604 (comment) which should have enough context/information.

[goodov]

LGTM other than the issue that @stephendonner pointed out re: Enabledd. Instructions should be good enough. At this point, most of QA should be able to figure out how to verify using the new method but I'll point them to our verifications via brave/brave-core#24604 (comment) which should have enough context/information.

The point here is so any developer who sees brave-variations for the first time can figure this on their own, it's not only about QA.

[kjozwiak]

LGTM other than the issue that @stephendonner pointed out re: Enabledd. Instructions should be good enough. At this point, most of QA should be able to figure out how to verify using the new method but I'll point them to our verifications via brave/brave-core#24604 (comment) which should have enough context/information.

The point here is so any developer who sees brave-variations for the first time can figure this on their own, it's not only about QA.

yup, makes sense 👍