Skip to main content

Two very good answers iI have come across are in thesehere:

  1. When to unit-test vs manual testWhen to unit-test vs manual test
  2. What not to test when it comes to Unit Testing?What not to test when it comes to Unit Testing?

JustificationThe justifications for avoiding percievedperceived overhead?:

  • Immediate Time/Cost Immediate saving for your company
  • Potential Time/cost saving in troubleshooting  /maintainability/extension in the long run even after youryou're gone.

Would you not want to leave a great product from your side as the proof of your quality of your work? Speaking in selfish terms  ,is is it not better for you that you do?

Two very good answers i have come across are in these

  1. When to unit-test vs manual test
  2. What not to test when it comes to Unit Testing?

Justification for avoiding percieved overhead?

  • Time/Cost Immediate saving for your company
  • Potential Time/cost saving in troubleshooting  /maintainability/extension the long run even after your gone.

Would you not want to leave a great product from your side as the proof of your quality work? Speaking in selfish terms  ,is it not better for you that you do?

Two very good answers I have come across are here:

  1. When to unit-test vs manual test
  2. What not to test when it comes to Unit Testing?

The justifications for avoiding perceived overhead:

  • Immediate Time/Cost saving for your company
  • Potential Time/cost saving in troubleshooting/maintainability/extension in the long run even after you're gone.

Would you not want to leave a great product from your side as the proof of quality of your work? Speaking in selfish terms, is it not better for you that you do?

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

Two very good answers i have come across are in these

  1. When to unit-test vs manual testWhen to unit-test vs manual test
  2. What not to test when it comes to Unit Testing?What not to test when it comes to Unit Testing?

Justification for avoiding percieved overhead?

  • Time/Cost Immediate saving for your company
  • Potential Time/cost saving in troubleshooting /maintainability/extension the long run even after your gone.

Would you not want to leave a great product from your side as the proof of your quality work? Speaking in selfish terms ,is it not better for you that you do?

Two very good answers i have come across are in these

  1. When to unit-test vs manual test
  2. What not to test when it comes to Unit Testing?

Justification for avoiding percieved overhead?

  • Time/Cost Immediate saving for your company
  • Potential Time/cost saving in troubleshooting /maintainability/extension the long run even after your gone.

Would you not want to leave a great product from your side as the proof of your quality work? Speaking in selfish terms ,is it not better for you that you do?

Two very good answers i have come across are in these

  1. When to unit-test vs manual test
  2. What not to test when it comes to Unit Testing?

Justification for avoiding percieved overhead?

  • Time/Cost Immediate saving for your company
  • Potential Time/cost saving in troubleshooting /maintainability/extension the long run even after your gone.

Would you not want to leave a great product from your side as the proof of your quality work? Speaking in selfish terms ,is it not better for you that you do?

Source Link
Aditya P
  • 3.5k
  • 2
  • 28
  • 42

Two very good answers i have come across are in these

  1. When to unit-test vs manual test
  2. What not to test when it comes to Unit Testing?

Justification for avoiding percieved overhead?

  • Time/Cost Immediate saving for your company
  • Potential Time/cost saving in troubleshooting /maintainability/extension the long run even after your gone.

Would you not want to leave a great product from your side as the proof of your quality work? Speaking in selfish terms ,is it not better for you that you do?