Skip to main content
Software Quality Assurance & Testing

Return to Answer

deleted 4 characters in body
Source Link
JAINAM
JAINAM
  • 1.8k
  • 3
  • 18
  • 39

CoupleA couple of guidelines in addition to above listed-listed items

  1. Test Steps
  2. Snapshots for each stepsstep if possible (In case you are working in remote teams, to avoid to-and-fro email communications)
  3. Expected result vs Actual Result
  4. Environment Details - OS, Hardware, Software, Build version
  5. Log fileLogfile entries  / valuesvalues
  6. Nice to have - Preliminary investigation  / analysisanalysis with supporting queries  / assumptionsassumptions to provide a couple of leads for a developer to check further
  7. Provide access to the test environment - URLs, Machines for the developer to check in case if needed
  8. Reference to BRD, FS, Design Document where implementation conflicts design  / requirementsrequirements
  9. Nice to Have - Triage Meeting / Issue Review meeting to run through the bugs once with the development team to provide a quick overview of issues before they start looking into it. F2F conversations are better than email  / chat coversationschat conversations sometimes
  10. Be Descriptive do not use AbbrevationsAbbreviations, No implicit assumptions. Callout your understanding of functionality and how it conflicts with implementation

Couple of guidelines in addition to above listed items

  1. Test Steps
  2. Snapshots for each steps if possible (In case you are working in remote teams, to avoid to-and-fro email communications)
  3. Expected result vs Actual Result
  4. Environment Details - OS, Hardware, Software, Build version
  5. Log file entries  / values
  6. Nice to have - Preliminary investigation  / analysis with supporting queries  / assumptions to provide couple of leads for developer to check further
  7. Provide access to the test environment - URLs, Machines for the developer to check in case if needed
  8. Reference to BRD, FS, Design Document where implementation conflicts design  / requirements
  9. Nice to Have - Triage Meeting / Issue Review meeting to run through the bugs once with the development team to provide a quick overview of issues before they start looking into it. F2F conversations are better than email  / chat coversations sometimes
  10. Be Descriptive do not use Abbrevations, No implicit assumptions. Callout your understanding of functionality and how it conflicts with implementation

A couple of guidelines in addition to above-listed items

  1. Test Steps
  2. Snapshots for each step if possible (In case you are working in remote teams, to avoid to-and-fro email communications)
  3. Expected result vs Actual Result
  4. Environment Details - OS, Hardware, Software, Build version
  5. Logfile entries/values
  6. Nice to have - Preliminary investigation/analysis with supporting queries/assumptions to provide a couple of leads for a developer to check further
  7. Provide access to the test environment - URLs, Machines for the developer to check in case if needed
  8. Reference to BRD, FS, Design Document where implementation conflicts design/requirements
  9. Nice to Have - Triage Meeting / Issue Review meeting to run through the bugs once with the development team to provide a quick overview of issues before they start looking into it. F2F conversations are better than email/chat conversations sometimes
  10. Be Descriptive do not use Abbreviations, No implicit assumptions. Callout your understanding of functionality and how it conflicts with implementation
Source Link
Siva
Siva
  • 2.8k
  • 18
  • 24

Couple of guidelines in addition to above listed items

  1. Test Steps
  2. Snapshots for each steps if possible (In case you are working in remote teams, to avoid to-and-fro email communications)
  3. Expected result vs Actual Result
  4. Environment Details - OS, Hardware, Software, Build version
  5. Log file entries / values
  6. Nice to have - Preliminary investigation / analysis with supporting queries / assumptions to provide couple of leads for developer to check further
  7. Provide access to the test environment - URLs, Machines for the developer to check in case if needed
  8. Reference to BRD, FS, Design Document where implementation conflicts design / requirements
  9. Nice to Have - Triage Meeting / Issue Review meeting to run through the bugs once with the development team to provide a quick overview of issues before they start looking into it. F2F conversations are better than email / chat coversations sometimes
  10. Be Descriptive do not use Abbrevations, No implicit assumptions. Callout your understanding of functionality and how it conflicts with implementation