Before a release, the author must perform a series of tests to make sure the track is working as intended. Simple errors like freezes or very bad respawn points ruins tracks. Here is a test list:

Testing

Test your track on the Wii

Many ct developers use Dolphin (Wii Emulator) to create and test tracks. Running the tracks on the Wii may change the behavior of textures and game play, and sometimes a freeze will be found.

Test in time trial, VS and online

Time trial and versus races are different. So some items like item boxes or wood boxes have a different behavior. Also make tests with 2 player offline on the split screen with enabled enemies to detect a Slow Motion Bug.

If possible, test the track online with some friend. There is for example a well known positioning bug, which only appears online.

If you have jumps over an abyss, test them in 50cc and also if you are small after a cloud. Also try with many different characters and vehicles, at least with a bike and kart of each weight class. Many tracks fail here.

Check the minimap

Is the minimap fully visible and centered in its view area? If not, fix the minimap positions. Wiimms SZS Tools can adjust the minimap automatically.

Check the check points

Make sure, that the check points are set following the new quadrilateral model and cover all drivable parts by convex quadrilaterals.

Test all possible routes of your track

Testing only the main road is a bad decision. Try to leave the main road and to find positioning and lap not counting bugs.

Test the item routes

Test all possible routes of your track, also all possible short cuts using mushrooms or other boost items. Use an item cheat for a long usage of Red shells and Bullet Bill. If you use a short cut, start Bullet Bill direct after entering the short cut to verify, if it follows the route. If this fails, your item routes are defined badly.

The height (Y value) of the item points are important. If it is to low, Bullet Bill tries to boring into the ground and some shells are dropped with unobvious reasons. If the height is to high, Bullet Bill flies in sky. Use tools with automated height correction to fix this kind of bugs.

Verify the enemy routes

Verify, that all enemies reach the finish line. Very often bad respawn points and especially their directions are the reason for enemy problems. Look on the minimap to find out, if the enemies use all defined routes.

Using AIParam

AIParam makes the AI drive faster than a human player can, adding to the challenge.

A drawback to it, besides making it very hard for a human player to win, is that AIParam is not a substitute for good Enemy Routes.

Check all respawn points

Check the position and direction of all respawn points. Fall down on every place you can. Use mushrooms to fall down far away from the main route. If 2 or more characters fall down at same location and time, they are respawned with an offset radius (up to 2000 units?). So a respawn point is really a respawn area and all of the area must be inside the road.

Make sure that all 12 start points are inside the road. Test at least first and last position with enabled CPU drivers.

Search for unintended shortcuts

Before releasing, it is wise to really explore your track (especially areas that most players would normally not go to). If an area outside the normal track walls is drivable then there is a chance that your track could develop an ultra shortcut, which could hinder its popularity and lead to its rejection from many popular custom track distributions.

Make a visual review

Make a visual review of your track by using wkmpt DRAW ... of Wiimms SZS Tools.

⇒ Details: KMP Editing/Visual Review

Think about face down roads

Triangles (faces) are directed and have only impact in one direction (keyword culling). If your roads (and also boost and other drivable KCL types) have triangles for the top and the bottom side, different glitches and bugs may appear:

Unwanted jump while driving over the road.
Hard changing of the driving direction if jumping down to the road.
Barrel rolling.
Curious camera jumping effects.
Underground views of cameras.

If you have some of these effects, try to remove the face down road triangles. Face down roads can be selected by the KCL Flag and its first normal (y value <0.0). Wiimms SZS Tools can remove such triangles automatically; see »KCL Tutorial (Wiimms Tools)« for details.

Think about item box places

Think about the item boxes groups (or rows). Use 3-6 groups with 4-6 item boxes in each group for a 3 lap round. There are some problems, if you do not so:

If a driver gets 18 or more items in an online race, all following items are mushrooms. This contradict the main idea of Mario Kart: Bad items for the player in first and good items for the players in the lower positions.
If a row have less than 4 items, only the first 2 players in a group get an item. And this is also bad for the game play.
Sometimes it may be tempting to place them just after a sharp turn, however if this is the case then going for the outside item boxes may cause a vehicle to crash into a wall or otherwise lose too much time for collecting the box to actually be worthwhile. Thus creating a problem very similar to that discussed in point number 2, above.
Classic tracks support sometimes only 1–2 item rows. But think in Wii dimensions: Items are the most important fun instrument of Mario Kart Wii. Be not afraid to add and move item rows; Nintendo does the same for its retro tracks.

The height of the itemboxes are also important. Be sure, that all itemboxes can be hit if driving with a small vehicle in reduced size (because of cloud or mega mushroom). Use tools with automated height correction to set the perfect height.