4 ms·
> Testing software after it gets deployed to production The first thing I though just after read the title was: "hm, it looks like a vendor lock"... > In 200
by app4soft 5y ago
> Testing software after it gets deployed to production
The first thing I though just after read the title was: "hm, it looks like a vendor lock"...
> In 2007, I was on site at the original iPhone launch at the only distribution center in the nation that was slated to ship the first iPhone.
... and as I see mentioning of Apple/iPhone, guess, I was not wrong with my first decision.
- joshhowen 5y agoHi, app4soft - I'm not sure I'm following your comment regarding "vendor lock". Would you mind explaining a bit further what you are referring to?
- app4soft 5y ago> Would you mind explaining a bit further what you are referring to? TL;DR: Software should not be tested or controlled by devs remotely on user's side. Otherwise it is "vendor lock".
- joshhowen 5y agoI see. So I'd like to make sure I'm understanding what you're saying - do you mind if I try to repeat back what I believe you're getting at? What I believe you are saying is that it isn't a good idea (in your opinion) to have developers that are not responsible for developing a particular piece of software to be in charge of creating automated testing for said product, as that is likely to result in the team responsible for building the software to be locked into that third party testing solution? I've got some clarifying thoughts but wanted to ensure I understood your thought pattern.