Deep Skills Internal
  • Welcome to Deep Skills
  • Deep Skills Organization
    • Quick Start Guide
    • About Deep Skills
      • Meetings & Workshops
        • 1:1 Meetings
        • Alignment and delegation
        • User journey
        • Presentation or landing page
        • Retrospective
      • Discord Server
  • Working at Deep Skills
    • Project-based work
      • General Etiquette
      • Roles & Responsibilities
        • Director
        • Expert
        • Contributor
        • Shadower
    • Getting Paid
      • Contributor Agreement
  • Skills and roles
    • Consultancy
      • Project owner
        • Workflow
          • Preparation
          • Consultation Call
          • Proposal Process
          • Payment Process
          • Retrospective
      • Data Steward
        • Workflow
          • Skills Interview Guide
      • DAO Steward
        • Workflow
          • Project Scoping Workshop
          • Retrospective Workshop
    • Operations
      • Operations Steward
        • Workflow
    • Engineering
      • Engineering PM
        • Workflow
      • Backend
        • Workflow
      • Frontend
      • DevOps
        • Workflow
      • Quality Assurance
        • Workflow
          • Project Testing
      • Solutions Architect
        • Workflow
    • Finance
      • Finance Director
    • Creating a new project →
      • Create a discrete project
        • Complete a discrete project
      • Create a recurring project
        • Complete a recurring project
      • Create a long-term project
  • Tools & Resources
    • Knowledge & Learning
    • Feedback
    • Historiography
Powered by GitBook
On this page
  • 1. Introduction meeting with architects (developers) to learn about the project.
  • 2. Get access to website and Figma(design).
  • 3. Project architecture and logic research.
  • 4. Test plan investigation.
  • 5. Test Cases investigation.
  • 6. Start project testing - Web and Mobile applications.
  • 7. First testing stage is finished.
  • 8. Bug report is created
  • 9. Looking for bug report updates on task board.
  • 10. If bug was fixed we close this ticket.
  • 11. When all bugs are resolved and closed
  • 12. Test summary
  • 13. If regression test was completed successfully we can do an application release!

Was this helpful?

  1. Skills and roles
  2. Engineering
  3. Quality Assurance

Workflow

PreviousQuality AssuranceNextProject Testing

Last updated 3 years ago

Was this helpful?

1. Introduction meeting with architects (developers) to learn about the project.

2. Get access to website and Figma(design).

3. Project architecture and logic research.

4. Test plan investigation.

5. Test Cases investigation.

6. Start project testing - Web and Mobile applications.

7. First testing stage is finished.

8. Bug report is created

(It can be created in Jira, GitHub or another soft)

9. Looking for bug report updates on task board.

When developers fixed bugs we should retest it again.

10. If bug was fixed we close this ticket.

If not we write a comment where the problem is described with photo and video attaching.

11. When all bugs are resolved and closed

Regression testing begins. It includes - full testing according to test cases.

12. Test summary

report about regression test: how many test cases were successfully done, how many test cases were failed.

13. If regression test was completed successfully we can do an application release!

Project Testing