Teaching Software Testing in Colombia

455 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
455
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Teaching Software Testing in Colombia

  1. 1. Teaching Software Testing in Colombia José Alejandro Betancur Test Manager, InterGrupo SA Lecturer, EAFIT University
  2. 2. José A. Betancur MBA, Eafit University B. Sc. Computer Science, Eafit University I’ve worked as: R+D Manager, Computer Architecture Professor, Thesis Advisor, process development consultant.
  3. 3. A little background
  4. 4. A little background • First known testing project was officially made in 1998 (localization of Quicken, Intuit Inc.)
  5. 5. A little background • First known testing project was officially made in 1998 (localization of Quicken, Intuit Inc.) • First team build with just the objective to test, 1999. Orbitel S.A.
  6. 6. A little background • First known testing project was officially made in 1998 (localization of Quicken, Intuit Inc.) • First team build with just the objective to test, 1999. Orbitel S.A. • First software testing company, 1999. Choucair Testing S.A.
  7. 7. Facts
  8. 8. Facts • 4 companies focused only on software testing services
  9. 9. Facts • 4 companies focused only on software testing services • around 300 software testing engineers
  10. 10. Facts • 4 companies focused only on software testing services • around 300 software testing engineers • very different “concepts” when you ask what they do every day.
  11. 11. Facts • 4 companies focused only on software testing services • around 300 software testing engineers • very different “concepts” when you ask what they do every day. • testing made is “functional testing”
  12. 12. Facts • 4 companies focused only on software testing services • around 300 software testing engineers • very different “concepts” when you ask what they do every day. • testing made is “functional testing” • 2 of these companies are starting to perform “technical tests”
  13. 13. Ok, here is where the challenge* start...
  14. 14. Ok, here is where the challenge* start... *problems, difficulties, discussions
  15. 15. Functional testing = Scripted Black Box testing
  16. 16. Technical tests = performance testing
  17. 17. Software Testing = Software Quality Assurance
  18. 18. one thing before continue...
  19. 19. one thing before continue... Just to check if we are in the same path
  20. 20. Testing is: “A technical investigation done to expose quality-related information about the product under test”*
  21. 21. Testing is: “A technical investigation done to expose quality-related information about the product under test”* *Cem Kaner
  22. 22. Quality is: “a value to some person.”
  23. 23. Quality is: “a value to some person.” *Gerald Weinberg
  24. 24. • Quality is not about implement the best practices (development or testing)
  25. 25. • Quality is not about implement the best practices (development or testing) • Quality is not about validate uses cases
  26. 26. • Quality is not about implement the best practices (development or testing) • Quality is not about validate uses cases • Quality is not about check every functionality
  27. 27. • Quality is not about implement the best practices (development or testing) • Quality is not about validate uses cases • Quality is not about check every functionality • Quality is not about...
  28. 28. { • Quality is about implement the best practices (development or testing) • Quality is about validate uses cases } • Quality is about check every functionality
  29. 29. Software { } Quality Assurance
  30. 30. and what’s the relation of all this with an BBST course?
  31. 31. Course Roadmap
  32. 32. Fundamental Issues
  33. 33. Bug Advocacy Fundamental Issues
  34. 34. Adv. Topics Bug Advocacy Bug Advocacy Fundamental Issues
  35. 35. Domain Testing Bug Advocacy Fundamental Issues
  36. 36. Function Testing Domain Testing Bug Advocacy Fundamental Issues
  37. 37. Scenario Testing Function Testing Domain Testing Bug Advocacy Fundamental Issues
  38. 38. Testing Techniques Bug Advocacy Fundamental Issues
  39. 39. Test Design Testing Techniques Bug Advocacy Fundamental Issues
  40. 40. Risk Specification Based Based Test Design Testing Techniques Bug Advocacy Fundamental Issues
  41. 41. Multivariable Testing Risk Specification Based Based Test Design Testing Techniques Bug Advocacy Fundamental Issues
  42. 42. Scripted Exploratory Multivariable Testing Risk Specification Based Based Test Design Testing Techniques Bug Advocacy Fundamental Issues
  43. 43. but...
  44. 44. • Every single course had to include a session to talk more about definitions, RUP point of view, CMMI verification and Validation PA’s, and the difference between SQA and Testing.
  45. 45. • When the course were delivered to Companies (Banks, Telecoms) they realize that functional testing is just part of what they need: the course has to be conducted more focused on unit test and automation testing.*
  46. 46. • When the course were delivered to Companies (Banks, Telecoms) they realize that functional testing is just part of what they need: the course has to be conducted more focused on unit test and automation testing.* * more tools oriented
  47. 47. • When the course were delivered to a Software Testing Company they start to change the way they sell their services, and start talking about acceptance testing, black box, performance testing.
  48. 48. • When the course were delivered to a Software Testing Company they start to change the way they sell their services, and start talking about acceptance testing, black box, performance testing. * more context oriented
  49. 49. The new course roadmap
  50. 50. Fundamental Issues
  51. 51. Bug Advocacy Fundamental Issues
  52. 52. Quality before design Bug Advocacy Fundamental Issues
  53. 53. Testing Techniques Quality before design Bug Advocacy Fundamental Issues
  54. 54. Test Design Testing Techniques Quality before design Bug Advocacy Fundamental Issues
  55. 55. Test execution Test Design Testing Techniques Quality before design Bug Advocacy Fundamental Issues

×