Skip to content

Latest commit

 

History

History
54 lines (34 loc) · 2.02 KB

qa.md

File metadata and controls

54 lines (34 loc) · 2.02 KB

Inplayer's QA Internship Program

SUBJECT >> DETAILS

1. SDLC and STLC

2. Agile and Waterfall Methods

3. Functional and Non-Functional Testing

4. Functional: Sanity, Smoke, Regression

5. Non-Functional: Performance, Load, Security Testing

6. Soft skills

7. Ownership of task

8. Use (test) scenario/ test cases/ test prioritisation >> writing, test prioritisation, negative scenarios

9. Reports for testing progress

10. Bug reporting >>

  • Defect_ID - Unique identification number for the defect.
  • Defect Description - Detailed description of the Defect including information about the module in which Defect was found.
  • Version - Version of the application in which defect was found.
  • Steps - Detailed steps along with screenshots with which the developer can reproduce the defects.
  • Reference - where in you Provide reference to the documents like: requirements, design, architecture.
  • Detected By - Name/ID of the tester who raised the defect
  • Status - Priority and severity

11. Ad-hoc testing, exploratory testing; types of testing >> staging, production, localhost

12. Regression testing

13. Why testing

14. Testing Life Cycle >>

  • Requirement Analysis - analysing the requirement
  • Test Planning - resources and time estimation
  • Test case development - analysing and evaluating scenarios based on communication with all integrated teams
  • Test Environment setup - to do smoke test
  • Test Execution - executing test cases bug reporting
  • Test Cycle closure - evidencing testing conclusions

15. Api testing >>

  • Return value based on input condition: it is relatively easy to test, as input can be defined and results can be authenticated
  • Update data structure: Updating data structure will have some outcome or effect on the system, and that should be authenticated
  • Modify certain resources: If API call modifies some resources then it should be validated by accessing respective resources

16. Test management tools - Testing Management Tools