| 1 |
This file contains various test plans when making changes to the code. |
| 2 |
These steps are intended to give people an idea of possible things to |
| 3 |
try out when changing the code. |
| 4 |
|
| 5 |
Please add to this file as you find bugs and develope some testing |
| 6 |
plan to verify the bugs. This is useful for future developers. |
| 7 |
|
| 8 |
Try to organize the tests into groups that exercise that specific |
| 9 |
area, eg, don't mix something that tests spell functionality in the |
| 10 |
same area that deals with map loading. |
| 11 |
|
| 12 |
------------------------------------------------------------------------------ |
| 13 |
Map Loading/Saving and Exit code. |
| 14 |
|
| 15 |
1) Enter map not loaded before. Does it load correctly. Leave an item there |
| 16 |
for future reference. |
| 17 |
2) Exit map and re-enter quickly. Is it loaded correctly? Is that item you |
| 18 |
left there? |
| 19 |
3) Exit map, and wait for it to swap out. Then re-enter. Is that item there. |
| 20 |
4) Repeat steps 1-3 with a per player unique map. |
| 21 |
5) Repeat steps 1-3 with a map that has the outdoor flag set |
| 22 |
6) Kill server, and re-run tests. |
| 23 |
|
