Updates zephyr test cases for edit file attachment

[yasserfaraazkhan]

e2e PR: mattermost/mattermost#29797

[saturninoabril]

Should we move each scenario as steps in Zephyr, such as **Step 2** to 6? With that, we can map each automated test as MM-T5654_1 to _6? Same comment to MM-T5655.

[yasserfaraazkhan]

Should we move each scenario as steps in Zephyr, such as **Step 2** to 6? With that, we can map each automated test as MM-T5654_1 to _6? Same comment to MM-T5655.

Hi @saturninoabril (can you help me if I got it right? )

You mean instead of Step_1, Step-2 in One file, have separate test files for all steps ?

[saturninoabril]

Should add **Step [n]** so this will be saved as step number in Zephyr and can be referenced as MM-T5654_4 in test report integration.

Suggested change

	### Scenario 4: User should be able to edit post message originally containing files
	1. Navigate to a Channel/Gm/DM where current user has a post with attachments.
	2. Click the "Edit" option in the post actions menu.
	3. Use the "Attach" button (paperclip icon) to upload a file or drag and drop a file into the editable area.
	4. Save the edited post.
	5. Verify the attachment is visible.
	**Step 4**
	### Scenario 4: User should be able to edit post message originally containing files
	1. Navigate to a Channel/Gm/DM where current user has a post with attachments.
	2. Click the "Edit" option in the post actions menu.
	3. Use the "Attach" button (paperclip icon) to upload a file or drag and drop a file into the editable area.
	4. Save the edited post.
	5. Verify the attachment is visible.

[saturninoabril]

You mean instead of Step_1, Step-2 in One file, have separate test files for all steps ?

You may modify as suggested at #201 (comment) or better organize into a separate test case so that a single test key does not contain too much scenarios.

[yasserfaraazkhan]

You mean instead of Step_1, Step-2 in One file, have separate test files for all steps ?

You may modify as suggested at #201 (comment) or better organize into a separate test case so that a single test key does not contain too much scenarios.

Got it Saturn
I'll add steps for these tests. I'll keep making more test files with concise scenarios in upcoming PRs