Lessons Learnedin Software QualityRayya Abu GhoshBelal Raslan
Lesson 1Am I QA or QC ?
Lesson 1Am I QA or QC ?How ?                                                 What?
Lesson 2Am I QC or Tester?
Lesson 2Am I QC or Tester?
Lesson 3What makes a good test engineer?AnalyticalCuriousFlexibleDetail orientedisiveDeciCommunicator
Lesson 3What makes a good test engineer?
Lesson 4Types vs. Levels of Testing
Lesson 4Types vs. Levels of Testing
Lesson 5Defining the scope of testWhat can be tested?What will be tested?Who will test it?Make it clear and sign offIntegrationFunctionalitySecurityPerformanceUsabilityCompatibilityGlobalization /i18n
Lesson 6Bugs detection vs. prevention
Lesson 6Bugs detection vs. prevention
Lesson 6Bugs detection vs. prevention
Lesson 7Smoke test first, it’s cheaper
Lesson 7Do smoke test first, it’s cheaper!
Lesson 8Write a bug that will be fixed
Lesson 8Write a bug that will be fixed
Lesson 8Write a bug that will be fixed
Lesson 9Bug Priority vs. Severity
Lesson 9Bug Priority vs. Severity
Lesson 10Never use bug tracking systems to measure performance
Lesson 11Test time estimates!
Lesson 11Test time estimates!
Lesson 12You will not find all the bugs
Lesson 13What documentation matters?
Lesson 13What documentation matters?
Lesson 15Keen to know more
Lesson 14Keen to know moreTrainings, sessions, open discussionsOnline groups, forums, sitesLean more about the businessLearn more about technology, toolsSDLC Processes (XP, agile, Iterative, Waterfall…)About users perspectives (usability)
Useful LinksSoftware Quality Engineers in Jordan GroupQuality Partners™Tech Jordan
Keep in touch Born to Teest!
Coming soon..session II

Lessons Learned in Software Quality 1

Editor's Notes

  • #16 Tester will gain more time by delivering incomplete build
  • #25 Acceptance Criteria