Skip to main content
Prompts Software QA Tester for Login Functionality

model evaluation user risk: low

Software QA Tester for Login Functionality

The prompt instructs the model to act as a software quality assurance tester for a new application, testing functionality and performance, writing detailed reports on issues or bug…

PROMPT 

I want you to act as a software quality assurance tester for a new software application. Your job is to test the functionality and performance of the software to ensure it meets the required standards. You will need to write detailed reports on any issues or bugs you encounter, and provide recommendations for improvement. Do not include any personal opinions or subjective evaluations in your reports. Your first task is to test the login functionality of the software.

REQUIRED CONTEXT

  • login functionality of the software

ROLES & RULES

Role assignments

  • act as a software quality assurance tester for a new software application
  1. Do not include any personal opinions or subjective evaluations in your reports

EXPECTED OUTPUT

Format
structured_report
Constraints
  • detailed reports on issues or bugs
  • provide recommendations for improvement
  • no personal opinions or subjective evaluations

SUCCESS CRITERIA

  • Test the functionality and performance of the software
  • Write detailed reports on any issues or bugs encountered
  • Provide recommendations for improvement
  • Test the login functionality

FAILURE MODES

  • No actual software provided, leading to hypothetical or invented tests
  • Risk of including personal opinions despite explicit rule
  • Undefined 'required standards' may cause inconsistent evaluations

CAVEATS

Dependencies
  • Access to the new software application
  • Implementation details of the login functionality
Missing context
  • Software application details (e.g., URL, UI description, backend specs).
  • Login requirements and expected behaviors.
  • Test environment or tools.
  • Success criteria or acceptance standards
Ambiguities
  • No description of 'the software' or how to access it.
  • Unclear how to perform testing without actual software access (e.g., simulate?).
  • 'Required standards' not defined.
  • Scope of 'login functionality' testing ambiguous (e.g., UI, security, performance metrics).

QUALITY

OVERALL
0.50
CLARITY
0.80
SPECIFICITY
0.50
REUSABILITY
0.40
COMPLETENESS
0.30

IMPROVEMENT SUGGESTIONS

  • Add a detailed description or mockup/URL of the software and login feature.
  • Specify test cases, edge cases, and performance metrics for login.
  • Provide a report template with sections for issues, bugs, and recommendations.
  • Introduce placeholders like '{functionality}' and '{software_description}' for reusability.
  • Clarify if testing should be simulated via hypothetical scenarios or requires real interaction.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR MODEL