<div dir="ltr">I'm assuming you're referring to testing backend drivers as opposed to database migrations (tests/test_sql_upgrade.py).<div><br></div><div style>Backend agnostic tests land in tests/test_backend.py. Backend-specific tests, overrides, etc belong in tests/test_backend_sql.py, tests/test_backend_kvs.py, etc.</div>
<div style><br></div><div style>Generally, you can't assume that keystone is backed by a database, however, as it's entirely possible to deploy without one.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Tue, Jul 9, 2013 at 10:55 AM, Akshat Kakkar <span dir="ltr"><<a href="mailto:the_akshat@yahoo.co.in" target="_blank">the_akshat@yahoo.co.in</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div style="font-size:12pt;font-family:arial,helvetica,sans-serif"><div>How to write unit tests in keystone for the methods which are directly calling the backend db? I understand that for testing purpose it should be a *fake db*, but how to do that in keystone?<br>
</div></div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><br></div>-Dolph
</div>