| Author |
Application testing
|
|
|
| I wondering what methods other use to test their applications at future
dates. Our application currently gets their date/time from the database
(sybase). We have been setting the box it runs on ahead to the times we
need to test at. Of course this basically stops others from testing
their applications because if they cut any transactions and then we set
the date back to normal there will be some messed on data on the box.
We don't like to change the application because this could lead to code
been left in by mistake.
| |
| Jim Douglas 2004-07-22, 8:57 am |
| But what if you don't change the date on the server?
"David" <Davidwork@ewerewrew.com> wrote in message
news:SmgLc.3$Xt4.486@news2.mts.net...
> I wondering what methods other use to test their applications at future
> dates. Our application currently gets their date/time from the database
> (sybase). We have been setting the box it runs on ahead to the times we
> need to test at. Of course this basically stops others from testing
> their applications because if they cut any transactions and then we set
> the date back to normal there will be some messed on data on the box.
> We don't like to change the application because this could lead to code
> been left in by mistake.
>
| |
|
| Sybase plays catch up if you don't reboot the server which could take it
quite awhile if your setting it a month or two in the future. One
options we have is to make sure all applications call a common Stored
Procedure that gets the date/Time from the server and just alter it when
testing
Thanks,
David
Jim Douglas wrote:
> But what if you don't change the date on the server?
> "David" <Davidwork@ewerewrew.com> wrote in message
> news:SmgLc.3$Xt4.486@news2.mts.net...
>
>
>
>
|
|
|
|