Any Test case for Function Changing Frquently

Replies to This Discussion

Permalink Reply by Malay Parikh on July 21, 2011 at 4:16pm

Hi,

Its only possible with same functionality related test cases.

Otherwise you have to consider new functionality and new test case and scenarios.

 

• ▶ Reply

Permalink Reply by Samrat Jha. on July 21, 2011 at 4:32pm

 

No ... test cases will not be written... and in general  Game testing is done using Exploratory and Ad-hoc testing .. so I don't think that the test cases will be written.............. 

 because  Test cases are written then they are reviewed and after approval they are execute ... but by then your functionality is going to change ........ so...  better to plan and execute at the same time.... 

• ▶ Reply

Permalink Reply by Teemu Vesala on July 21, 2011 at 4:48pm

Now the case depends how things are done. Let's expect that there is file which tells following things: When next game starts, url for game. Then after that date server automatically returns the next game. (I'm expecting that change is done automatically.) Then test case requires following things: a) plenty of time or b) possibility to change date at server. If the date changing is not possible, then my test case contained two lines at configuration file. First line has started 'yesterday' and second line will start new game next day. Testing that would need 2 days (or acctually 5 mins from both of them). This way doing the longer test is not reasonable choice.

 

If there is possibility to change the time at server, then I'd first set date to current date & time. Then installed the configuration file as in previous. Check that 'current game' is ok. After that I'd change the clock to next date and check it's ok. That is only basic case. You should do more extensive testing if date changing is possible. (E.g. leap years, new year, non-leap years, and so on...) Use your own imagination and knowledge about critical dates.

• ▶ Reply

Permalink Reply by jaffamonkey on July 21, 2011 at 7:55pm

Of course test case can be written for functions that change frequently - this is normal - applications functions can and do change periodically.  Websites change - that is the nature of websites.  Even one-off function testing should be documented as a test case.

 

Just keep in mind that testing needs an audit trail - ad hoc undocumented testing doesnt figure in regression testing, and won't help you if a client finds issue on live system, then asks you what testing has been done in that area.  Answering "adhoc undocumented testing" will not impress the client, however justified you think it is.

 

Just step back from the function - and try writing it from higher level.  You say the games will be changed - are you talking about functionality within the game?  And if so, is the game functionality shared across any other games?

• ▶ Reply