Quality Assurance

Question 1

Quality Assurance

Answer 1

• process of aiming to maintain high-quality standards throughout the creation process
• vital part of the development process
• involves monitoring all development stages against relevant standards and project requirements.
• involves producing necessary documentation to track quality efforts.

Question 2

Agile Projects

Answer 2

• has a much more flexible way of breaking down the tasks that need to be done to complete a project
• Breaks projects into
  -Themes or initiatives,
  
  • Epics or projects
  • Tasks or issues
• Themes:
  
  • one of the major goals of the project.
  • a long term objective that is a major and significant component of the project
  • viewed as a major strategic business objective
• Epics:
  
  • larger body of work that constitutes one of the main components of a theme
  • Epics are measurable – you can determine when complete
• Issues
  
  • one of the tasks that needs to be completed as part of an epic
  • a small enough task that it can be performed in a few days or a week.
    -

Question 3

Agile Project breakdown

Answer 3

Theme > Epic > Issue > Child Issue

Question 4

User Stories

Answer 4

• convey the user’s perspective to the developer, let developers see how it fits into the big picture

Question 5

Investable User story

Answer 5

• Independent - the story should not depend on other stories and can be completed on
  its own,
• Negotiable - it should open a conversation with the customer to invite refinement and
  change,
• Valuable - it should provide significant value to the project,
• Estimable - it should be estimated to be the right size for an issue,
• Small - it should be able to be completed in a few days,
• Testable - it should have clear acceptance criteria so tests can be written to verify it.

Question 6

Software Test Plan

Answer 6

• one of the most fundamental documents for software testing.
• project plan for the system testing
• It is really the instruction manual for the testing process
• includes:
  description: Outlines how testing will be executed

objectives: Defines what will be tested and the expected outcomes

scope: Specifies which parts of the software will be tested

schedule: Details the timeline and sequence of testing activities

list of risks in the project and how they can be mitigated

a list of the hardware and software resources necessary to conduct the testing

list of the roles and skills of the people required to do the testing

Question 7

Test Strategy

Answer 7

• a short, separate document which is often written before the test plan.
• define the major test objectives and to make sure that the test aligns with the
  organizational needs

Question 8

Test Plan Layout

Answer 8

Test plan > Environment > Features to be Tested > Features not Tested > Testing Procedure > Defect Management > Risks

Question 9

Jira

Answer 9

• popular tool for managing teams working on software projects
• It tracksIssues might include:
  
  • Features which need to be built,
  • Design documents which need to be written,
  • Software tests which need to be written,
  • Software tests which need to be executed
• Capabilities:
  
  • Add users to your project, creates and assign issues, moving issues through the Kanban columns, notify team members of issue status