Quote from byteme:
You mean, standard software development best practices like build files, automated unit and functional testing, continuous integration etc.?
Before answering your question:
Somehow I still got notification of this post after turning off notification on this thread. Or maybe you posted this before I disabled.
So I will attempt to answer your question. But first, let me explain that my PM is disabled. And notifications on this thread will stop. So any other questions will be better in a different thread.
But it's kind of only once a week that I search for threads with the keyword "tickzoom".
I have this policy to prevent distractions except from members or candidate members who post tickets in the members-only wiki or email me directly or ask questions in the members only forum.
The answer to all your questions is yes. You call those "standard" but it's amazing how few companies have really adopted those and especially TDD.
Frankly, it's nearly impossible to retroactively setup high coverage automated tests on systems that weren't designed with TDD (test driven development) from the beginning.
But since that's how TZ was built from the beginning, it's almost stunning how quickly TZ can innovate (also partly due to the architecture) new features and enhancements requested.
That's all because the Q&A process for a new release take minutes, and has far higher quality than most Q&A and regression test departments.
But, even though members love the instant updates, that's still far from being the best part according to them.
Ta ta for now. It's time for me to get back to working enhancement/defect tickets on TZ.
Sincerely,
Wayne