Hey thanks for the AMA. What do you think about having TDD(unit tests) Vs testing after writing code(manual and E2E automation). Do you think it's more cost effective to have TDD rather than testing after writing code?
On a broader level how do you think the testing is evolved from when you started working? And what practice would you recommend?
Started out teaching English at Embry-Riddle.
Graded 10,000 essays.
Lesson learned.
Became a mathematics teacher.
Discovered computing.
Never looked back.
Location
Houston TX
Education
Stetson University: B.A., M.A. in English; M.S. in mathematics
Unit testing is essential, whether TDD or a little more tardy. For my GitHub projects and their gems, I almost always do TDD (but sometimes I'm a little tardy).
Most agree that some manual testing is also essential, especially exploratory testing.
I'm not a fan of E2E, but instead prefer crafty testing of the segments along the E2E path. E2E is expensive to build, often runs slowly, and can make errors difficult to isolate.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey thanks for the AMA. What do you think about having TDD(unit tests) Vs testing after writing code(manual and E2E automation). Do you think it's more cost effective to have TDD rather than testing after writing code?
On a broader level how do you think the testing is evolved from when you started working? And what practice would you recommend?
Unit testing is essential, whether TDD or a little more tardy. For my GitHub projects and their gems, I almost always do TDD (but sometimes I'm a little tardy).
Most agree that some manual testing is also essential, especially exploratory testing.
I'm not a fan of E2E, but instead prefer crafty testing of the segments along the E2E path. E2E is expensive to build, often runs slowly, and can make errors difficult to isolate.