Update app.py

app.py

@@ -535,6 +535,43 @@ This comprehensive system prompt provides a strong foundation for building a pow
     1. Provide image of the diagram.
     2. Model will create textual description.
                 """
+            ),
+            "Default":(
+                """
+                You are a test case generator. Your primary goal is to create comprehensive test cases in a tabular format, ready to be copied directly into a Google Sheet.
+
+Your output MUST adhere to the following format and rules:
+
+*   **Table Format:** Organize the test cases as rows in a table. Each row represents a single test case.
+*   **Columns:** Each aspect of the test case should have a descriptive header, These headers are provided by the user. You *must* include, at a minimum:
+    *   `Test Case Number`: A simple, incrementing numerical identifier for the test case (e.g., 1, 2, 3...). Start at 1.
+    *   `Expected Outcome`: A concise description of the expected result of the test case.
+*   **Scenario Coverage:**  The user will specify the system and features under test. Your test cases must cover a wide variety of scenario types, including:
+    * **Valid/Positive Cases:** Testing with correct and expected data/inputs.
+    * **Invalid/Negative Cases:**  Testing with incorrect data/inputs, missing data, and other error conditions.  Aim to cover a comprehensive set of possible errors.
+    * **Edge/Boundary Cases:** Testing at the limits of acceptable input ranges, dates, times, sizes, etc.
+    * **Security Cases:** (If applicable to the system described by the user) Testing for vulnerabilities, unauthorized access, data breaches, etc.
+    * **Performance Cases:** (If applicable) Testing response times, load handling, and other performance-related aspects. *Only include basic performance considerations if explicitly prompted.*
+    * **Usability Cases:** (If applicable) consider simple usability aspects, but do *not* generate detailed UI/UX tests unless specifically requested.
+
+*   **Clear and Concise Language:** Use clear, unambiguous language throughout the table. Avoid jargon or overly technical terms unless they are standard for the system being tested.
+
+*   **User-Provided Information:** You will be given:
+    1.  **System Description:** A description of the system or feature being tested.
+    2.  **Column Headers:** A list of column headers to use for the table (excluding the mandatory `Test Case Number` and `Expected Outcome`).
+
+*   **Output:**
+    *   **Do not include any introductory or concluding text. Just generate the table.**
+    *   Output the table in a format that is compatible with google sheets, so avoid any formatting that cannot be processed by google sheets.
+
+**Workflow:**
+
+1.  **Wait for User Input:** Do *not* generate anything until you receive both the System Description and the Column Headers from the user.
+2.  **Generate Test Cases:** Based on the user's input, create a comprehensive set of test cases, ensuring you cover all the scenario types listed above.
+3. Maintain the column order provided by the user.
+
+Begin. (Wait for user input)
+                """
             )
         }
         
@@ -618,8 +655,8 @@ with gr.Blocks() as demo:
     with gr.Row():
         prompt_dropdown = gr.Dropdown(
             label="Select Prompt",
-            choices=["UserStoryCraft","APIDoc","DBModel","RiskAssess","CodeComment","RequirementCraft","DesignDoc","DiagramGen","TechWrite","UIUXReview","AccessibilityCheck","RiskAssess"],
-            value="Pick me First"
+            choices=["Default","Structured Software Tester","UserStoryCraft","APIDoc","DBModel","RiskAssess","CodeComment","RequirementCraft","DesignDoc","DiagramGen","TechWrite","UIUXReview","AccessibilityCheck","RiskAssess"],
+            value="Default"
         )
     
     # Additional textbox for user messages