| 88 | == Features of EdenTest == |
| 89 | |
| 90 | === Settings inspection === |
| 91 | You can fetch deployment settings from the server (only if you have admin permissions for that server) by doing the following: |
| 92 | {{{ |
| 93 | ${deployment settings} = Get Deployment Settings template |
| 94 | ${TEMPLATE}= Get From Dictionary ${deployment settings} template |
| 95 | }}} |
| 96 | For this to work, there should a function defined as `get_template()` defined in '''s3cfg.py''' |
| 97 | |
| 98 | === Database Inspection === |
| 99 | You can do database inspection inside !EdenTest (only for local servers). Keywords doing database querying, assertions etc should be defined in `edentest_database_local.py`. There are already a few helper keywords defined there to make it easy to do querying. |
| 100 | Eg: |
| 101 | {{{ |
| 102 | Row count is equals x (s3db.asset_asset.id > 25) 16 |
| 103 | }}} |
| 104 | This would fail/pass depending wether the query is true or false. |
| 105 | |
| 106 | === Database Rollback === |
| 107 | To be implemented |
| 108 | |
| 109 | === Deliver traceback of internal error pages === |
| 110 | If there is a ticket generated, !EdenTest gives back the traceback inside the logs and shows it on the console. If there is no traceback generated a screenshot is taken instead of the error and stored in the report. |
| 111 | |