and you reckon that the beta testers can find every single bug in the application? I think not. Even so BP releases are usually flawless as they have been tested but every now and then something slips through though usually minor. BP is far in a way better than MD releases used to be (can't say anything about the last 2 years worth). I have never had to use the roll back facility but it is comforting to know that it is there wouldn't you say
N

Mario Ruiz wrote:
Hi Cedric,

But we are not talking just a bug, you are talking about a total
application roll-back, a kind of a Panic Button where the bug is of a
magnitude that it forces you to use a roll-back button. Are we not?

It begs the question, should you have that release in your production PC
in the first place?   or should it have been stress tested on a
Non-production machine first?.

On your other point, one does not needs dozens of testers to test an
application.  Depending on the technology used by the application there
are automatic tools to do that.


Mario



Cedric Meyerowitz wrote:
Mario
This occurs because different people have different configirations etc.  Not
every minute detail can be testyed unless one has dozens of testers etc.
Some functions of my programs I might only use once a month, some weekly &
some daily.  If you look at what some users say about the same product: Some
users find it bug free after an upgrade, others find it has new bugs.  Why ?
All depends on each system.

Even motor cars have recalls - and they cost far more than PC software.
These problems were not found on initial testng of the car.  Can you then
say it is a crap car because there was a recall ?

Cedric


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Mario Ruiz
Sent: Tuesday, 3 July 2007 8:41 PM
To: General Practice Computing Group Talk
Subject: Re: [GPCG_TALK] Wish list- Medical Software


Marvelous?,

Why would anyone code a "Downgrade" in an application?

It speak tons of the Unit/Apps Testing process quality in the first place,
and then leave it to the user to clean up the mess.  Is that marvelous?

Is one thing to roll-back data updates (ie rdbms), but a totally different
thing to roll-back an application upgrade.  if testing is not complete, one
never releases the upgrade it in the first place.

I'm not a purist but to me that really sucks.

mario



Cedric Meyerowitz wrote:
That is what happens to BP users too. Further in the unlikely event that a program update has a bad bug that was missed, with a double click we go back to the previous edition - thus no down time, trying to uninstall the new program & then installing the old one, crossing fingers etc. Marvelous.

Cedric


_______________________________________________
Gpcg_talk mailing list
[email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk


_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk



_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk


_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk

Reply via email to