Quality Assurance

 I am a Quality Assurance tester at my job. Quality Assurance or QA is a group of processes in place to make sure that an organization document what they do and they do what they document (focus on defect prevention). In other words, making sure the product meets the requirements of what is documented. In order to do this successfully, you must know the basics.Roles of a QA Tester:

• Understand the Business Requirements
• Document the Test Plan
• Document the Test Cases
• Setting up the Test Environment
• Receiving Training on Product
• Execution of the Test Cases
• Defect Reporting and Tracking
• Writing summary Reports
• Participating in meetings, walkthroughs, and demos

SDLC - Software Development Life Cycle:

• Project Definition: (Initiate the project) - Gather business requirements
• Define the System: User Requirements Definition
• Design the System: System Requirements Definition
• Analysis and Design: Pre-development Phase
• Build/Test System: Development and Testing Phase
• Deploy the System: Implementation and Training
• Sustainment: Support the System (after software is in production)

Phases of Testing:

• Unit Testing
• Unit Integration Testing
• System Testing
• System Integration Testing
• User Acceptance Testing

Different Types of Testing:

• Waterfall Model
  • It's the less iterative and flexible approaches.
• Spiral Model
  • Developed by Boehm (1988)
  • Much More Flexible then Waterfall
  • Concept - Each portion of the product and each level of elaboration involves the same sequence of steps (cycle).
  • Each cycle ends with a review involving the key members.
• Agile/Scrum Model
  • Traditional approaches like Waterfall don't allow for feedback early on in the process.
  • Scrum seeks out transparency from the start of the project.
  • Scrum Allows for continuous improvement by giving teams many chances to learn from successes and failures.
  • Scrum allows for earlier delivery to market.