| 1 |
<!doctype html> |
| 2 |
<html lang="en"> |
| 3 |
<head> |
| 4 |
<meta charset="utf-8"> |
| 5 |
<title>jQuery UI Tests</title> |
| 6 |
<link rel="stylesheet" href="../../themes/base/jquery.ui.core.css"> |
| 7 |
<link rel="stylesheet" href="../../themes/base/jquery.ui.theme.css"> |
| 8 |
<link rel="stylesheet" href="index.css"> |
| 9 |
<script src="jquery-1.9.1.js"></script> |
| 10 |
<script src="index.js"></script> |
| 11 |
</head> |
| 12 |
<body> |
| 13 |
|
| 14 |
<div id="main"> |
| 15 |
<h1>jQuery UI Tests</h1> |
| 16 |
<div> |
| 17 |
<h2>Unit Tests</h2> |
| 18 |
<p><a href="unit/index.html">Unit tests</a> exist for all functionality in jQuery UI. |
| 19 |
The unit tests can be run locally (some tests require a web server with PHP) |
| 20 |
to ensure proper functionality before committing changes. |
| 21 |
The unit tests are also run on <a href="http://swarm.jquery.com/user/jqueryui">TestSwarm</a> |
| 22 |
for every commit.</p> |
| 23 |
|
| 24 |
<h2>Visual Tests</h2> |
| 25 |
<p><a href="visual/index.html">Visual tests</a> only exist in cases where we can't verify proper functionality |
| 26 |
with unit tests. These may be either purely visual or just hard to automate. |
| 27 |
Most visual tests will provide a description of what is happening on the page |
| 28 |
and what to look for.</p> |
| 29 |
</div> |
| 30 |
</div> |
| 31 |
|
| 32 |
</body> |
| 33 |
</html> |
Parent Directory
| 
Revision Log