Answers.Body: <p>Think like the user from hell.</p>
  <ul>
  <li>Check that it dose what it should. (knowledge of the spec is needed for this one)</li>
  <li>Check that you can achieve the goals of a user, easily. (user insight is needed for this one)</li>
  <li>Check that it does not break, including giving wrong results (some sort of insight of what can go wrong in the software/hardware is useful for this one).</li>
  </ul>
  <p>Depending on which of the roles that you will be doing. You may benefit from:</p>
  <ul>
  <li>Legal knowledge: it does not do what you want, but it meets the spec, so hand over the moneys.</li>
  <li>Business/user experience, that is having a deep knowledge of the users of the system. What task are they trying to get done. What is the easiest way to get it done.</li>
  <li>Programming experience. I would leave these tests to the programmers.</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-09-16T12:29:59.333Z
Answers.LastActivityDate: 2023-09-16T12:35:33.287Z
Answers.LastEditDate: 2023-09-16T12:35:33.287Z
Answers.UserDisplayName: ctrl-alt-delor
Body: <p>Writing Quality Assurance course test scripts for software products is a critical part of ensuring the quality and reliability of the software. Test scripts are sets of instructions that QA testers follow to verify that the software functions correctly and meets its requirements.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-09-08T15:24:53.237Z
Comments.Text: This is rather broad and I'm not really sure what you're asking about here. Can you narrow the question down to specific technologies or domains? Thanks. QA test scripts for web apps in Playwright is totally different than desktop or mobile QA test scripts.
Comments.UserDisplayName: ggorlen
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-09-15T01:01:44.557Z
Comments.Text: Normally in software we just jump in and flail around until we get better at it.
Comments.UserDisplayName: Scott Rowe
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-09-16T12:23:12.633Z
Comments.Text: You can't prove a negative: you can not prove the absence of bugs. You can reduce bugs, but doing it at a late stage is too late. The software devs need to adopt practices that reduce defects. They need to test their own code. Also, scripts should be automated, humans should be un-scripted using intuition.
Comments.UserDisplayName: ctrl-alt-delor
Tags: <unit-testing>
Title: How do I learn how to write QA test scripts for software products?
ThreadText: # How do I learn how to write QA test scripts for software products?
  
  (Asked by: username_0 on 2023-09-08)
  
  Writing Quality Assurance course test scripts for software products is a critical part of ensuring the quality and reliability of the software. Test scripts are sets of instructions that QA testers follow to verify that the software functions correctly and meets its requirements.
  
  **Tags:** unit-testing
  
  > **Comments:**
  > **username_1**: This is rather broad and I'm not really sure what you're asking about here. Can you narrow the question down to specific technologies or domains? Thanks. QA test scripts for web apps in Playwright is totally different than desktop or mobile QA test scripts.  
  > **username_2**: Normally in software we just jump in and flail around until we get better at it.  
  > **username_3**: You can't prove a negative: you can not prove the absence of bugs. You can reduce bugs, but doing it at a late stage is too late. The software devs need to adopt practices that reduce defects. They need to test their own code. Also, scripts should be automated, humans should be un-scripted using intuition.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2023-09-16. Score: 1
  
  Think like the user from hell.
  
  * Check that it dose what it should. (knowledge of the spec is needed for this one)
  * Check that you can achieve the goals of a user, easily. (user insight is needed for this one)
  * Check that it does not break, including giving wrong results (some sort of insight of what can go wrong in the software/hardware is useful for this one).
  
  Depending on which of the roles that you will be doing. You may benefit from:
  
  * Legal knowledge: it does not do what you want, but it meets the spec, so hand over the moneys.
  * Business/user experience, that is having a deep knowledge of the users of the system. What task are they trying to get done. What is the easiest way to get it done.
  * Programming experience. I would leave these tests to the programmers.
  
  
  ---
  
  