# User Engine - Login Engine testing

**URL:** <https://www.ruby-forum.com/t/user-engine-login-engine-testing/63831>\
**Category:** Engines\
**Created:** [January 21, 2006, 10:26pm UTC](https://www.ruby-forum.com/t/user-engine-login-engine-testing/63831 "2006-01-21T22:26:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![joshua\_s](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/779978/32.png) [@joshua\_s](https://www.ruby-forum.com/u/joshua_s)\
**Post date:** [January 21, 2006, 10:26pm UTC](https://www.ruby-forum.com/t/user-engine-login-engine-testing/63831/1 "2006-01-21T22:26:17Z")

</div>

Is it possible that the User Engine plugin breaks the Login Engine  
tests? Yesterday when I just had the Login engine the tests had no  
errors. Today, after the installation of the user engine, the tests are  
all broken.

I’m trying to dive deeper into the Login tests, but I’m pretty new to  
testing in general and I’m not exactly sure what I’m looking for. I’m  
thinking that I need to modify the Login tests to include the usernames  
and passwords used with the bootstrap for the User Engine. I think the  
tests might be failing because the users created don’t have permissions  
in user\_roles table.

Has anyone experienced anything like this? Does anyone think I’m on the  
right track?

I guess a bigger question is if the User engine is layered on, or  
modifies the Login engine, are the test rewritten in such a way that the  
entire package works? I would think that an enhancement shouldn’t break  
it’s dependencies tests. Anyways, it’s all great stuff, I’m trying to  
get the testing tight.

---

<div class="post-metadata">

**Author:** ![joshua\_s](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/779978/32.png) [@joshua\_s](https://www.ruby-forum.com/u/joshua_s)\
**Post date:** [January 21, 2006, 10:34pm UTC](https://www.ruby-forum.com/t/user-engine-login-engine-testing/63831/2 "2006-01-21T22:34:23Z")

</div>

The testing situation for the UserEngine in general, and certainly for  
the UserEngine-on-top-of-the-LoginEngine could almost certainly be  
tightened up. I would actually expect the LoginEngine tests to fail  
with the UserEngine installed, since the LoginEngine won’t know  
anything about the new restrictions on access.

I would suggest that the UserEngine probably needs to have adapted  
versions of the LoginEngine’s tests, if the current UserEngine tests  
don’t provide sufficient coverage… it’s definitely an area that  
needs work.

- james