sandeeprao

 Profile Answers by sandeeprao 

• Jul 9th, 2011

 

You need to change the database timing , by using SQL Query. This is the only way you can test the application

Mahadevan

• Sep 20th, 2011

 

if they validate only 12 o clock then we can change the system date to 12 o clock and test the application.

mithr17

 Profile Answers by mithr17 

• Oct 17th, 2011

 

You should use both the cases (sql query and changing system date) to test this requirement. You could create a macro for the SQL query and run it each time you'd like to test it.

mit

• Oct 13th, 2016

 

1. Wait for the 12 o clock then check the functionality
2. Change the date and time using SQL query then check the functionality
3. If application depends on system date then change the date and time and check the functionality
4. Also change the suitable time zone and then check the functionality

Sugumar

• Jun 21st, 2017

 

Yes, you can change the device date & time to near time when applicaiton expires

Burra Aparna

• May 29th, 2018

 

1. Check whether the application is exactly closed at 12 mid night by waiting.
2. Check whether the clock behaviour is changed by changing the time in the platform we are using.
3. Check whether any cheat codes are accepted by the application
4. Check whether the use is able to access the app even after the dead line.
5. Check whether the app is able to take a lot of load for a greater period within the deadline without any lag in response time.
6. Check whether the app is working for morning 12 noon.
7. Check whether the app differentiates am and pm or not and act accordingly.
8. Check whether the apps time and the platform time if do not match the app works or not?
9. Check whether even after the expiry it is working or not.
10. Check after expiry whether the app is accessible or not