Assuming that you are the world's best Quality Analyst, do the following tasks:
1. Read the requirement details of a feature to be developed given in triple quotes and break that into contextually important tasks.
2. Order the tasks by some priority from most to least important.
3. For every task, write the steps to verify it via manual testing and what should be the expected result that one should verify.
4. Make as many test steps as possible for each test case, but strictly do not repeat the content and meaning in each of those test steps.
5. Do not merge multiple actions into one test step. Keep them as separate steps.
6. Each test step must be crucial, such that not following it will fail the entire test case.
7. Each test case must have one and only one purpose. They must be a series of steps, and one single assertion in the end.
8. The test cases must not couple scenarios. For example, correct and incorrect scenarios must be two separate cases, not a single one. Edge cases must all be part of individual test cases.
9. Return the result in a valid JSON format like this. You must match this format exactly, and nothing else must be output that is outside this.
    format.
    [
        {{
            ""ReasonOfImportance"": ""Explain why you ranked it higher than others"",
            ""TestCaseTitle"": ""Title of what part of the feature we are testing"",
            ""Steps"": [{{
                ""ActionToPerform"": ""Describe the user action"",
                ""ExpectedBehaviour"": ""Describe the expected behavior""
            }}]
        }}
    ]
10. The first word of each ""ReasonOfImportance"" must be an action word, such as "Assert", "Check", "Verify", "Create", "Delete", "Update", "Check" and similar. This action must also be fulfilled by the last step of the test case.
11. The ""ReasonOfImportance"" and ""TestCaseTitle"" should be straightforward and mean exactly what is being done in that test case.
12. Try to generate as many test cases as you think are feasible (not more than <$PLACE_HOLDER_MAX_TC_COUNT$>) to cover every aspect of feature, but strictly do not repeat the content and meaning in each of those test cases.
13. Print the JSON output only. You must not print a single word other than that.
14. The output must not contain anything outside the JSON format. I do not want any explanations, descriptions, conversations, etc. Output only the JSON and nothing else.

Feature:
""""
{{PLACE_HOLDER_REQ_DESC}}

{{PLACE_HOLDER_REQ_ATT}}
""""