# Uninitialized constant Test error when running Fitnisse ruby

**URL:** <https://www.ruby-forum.com/t/uninitialized-constant-test-error-when-running-fitnisse-ruby/180374>\
**Category:** Ruby\
**Created:** [December 18, 2009, 7:11pm UTC](https://www.ruby-forum.com/t/uninitialized-constant-test-error-when-running-fitnisse-ruby/180374 "2009-12-18T19:11:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![arti\_singh](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/ba9def/32.png) [@arti\_singh](https://www.ruby-forum.com/u/arti_singh)\
**Post date:** [December 18, 2009, 7:11pm UTC](https://www.ruby-forum.com/t/uninitialized-constant-test-error-when-running-fitnisse-ruby/180374/1 "2009-12-18T19:11:22Z")

</div>

has anyone seen this error before? I have no idea on how to fix I have  
all but exhausted myself looking for the solutions to this

uninitialized constant Test  
C:/Documents and  
Settings/asingh/Desktop/QA/oriontests/orion\_login.rb:1:in `' C:/Ruby/Ruby1.9/lib/ruby/gems/1.9.1/gems/fit-1.2/lib/fit/fixture_loader.rb:65:in`require’  
C:/Ruby/Ruby1.9/lib/ruby/gems/1.9.1/gems/fit-1.2/lib/fit/fixture\_loader.rb:65:in  
`require_file' C:/Ruby/Ruby1.9/lib/ruby/gems/1.9.1/gems/fit-1.2/lib/fit/fixture_loader.rb:41:in`block in find\_class’  
C:/Ruby/Ruby1.9/lib/ruby/gems/1.9.1/gems/fit-1.2/lib/fit/fixture\_loader.rb:29:in  
`each' C:/Ruby/Ruby1.9/lib/ruby/gems/1.9.1/gems/fit-1.2/lib/fit/fixture_loader.rb:29:in`detect’  
C:/Ruby/Ruby1.9/lib/ruby/gems/1.9.1/gems/fit-1.2/lib/fit/fixture\_loader.rb:29:in  
`find_class' C:/Ruby/Ruby1.9/lib/ruby/gems/1.9.1/gems/fit-1.2/lib/fit/fixture_loader.rb:14:in`block in find\_fixture\_class’  
C:/Ruby/Ruby1.9/lib/ruby/gems/1.9.1/gems/fit-1.2/lib/fit/fixture\_loader.rb:14:in  
`collect' C:/Ruby/Ruby1.9/lib/ruby/gems/1.9.1/gems/fit-1.2/lib/fit/fixture_loader.rb:14:in`find\_fixture\_class’  
C:/Ruby/Ruby1.9/lib/ruby/gems/1.9.1/gems/fit-1.2/lib/fit/fixture.rb:82:in  
`find_class' C:/Ruby/Ruby1.9/lib/ruby/gems/1.9.1/gems/fit-1.2/lib/fit/fixture.rb:138:in`get\_linked\_fixture\_with\_args’  
C:/Ruby/Ruby1.9/lib/ruby/gems/1.9.1/gems/fit-1.2/lib/fit/fixture.rb:92:in  
`do_tables' C:/Ruby/Ruby1.9/lib/ruby/gems/1.9.1/gems/fit-1.2/lib/fit/fit_server.rb:93:in`process’  
C:/Ruby/Ruby1.9/lib/ruby/gems/1.9.1/gems/fit-1.2/lib/fit/fit\_server.rb:24:in  
`run' C:/Ruby/Ruby1.9/lib/ruby/gems/1.9.1/gems/fit-1.2/bin/FitServer.rb:5:in`’

---

<div class="post-metadata">

**Author:** ![arti\_singh](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/ba9def/32.png) [@arti\_singh](https://www.ruby-forum.com/u/arti_singh)\
**Post date:** [December 18, 2009, 8:58pm UTC](https://www.ruby-forum.com/t/uninitialized-constant-test-error-when-running-fitnisse-ruby/180374/2 "2009-12-18T20:58:34Z")

</div>

On 18.12.2009 19:11, Arti S. wrote:

> has anyone seen this error before? I have no idea on how to fix I have  
> all but exhausted myself looking for the solutions to this

> uninitialized constant Test

Your suit of tests is lacking a require, somewhere.

The details depend on what you use for testing, but one option is

require ‘test/unit’ # Ruby’s included test suit

That requires should be in every file doing tests, ideally, so you can  
run them independently.

---

<div class="post-metadata">

**Author:** ![arti\_singh](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/ba9def/32.png) [@arti\_singh](https://www.ruby-forum.com/u/arti_singh)\
**Post date:** [December 18, 2009, 10:59pm UTC](https://www.ruby-forum.com/t/uninitialized-constant-test-error-when-running-fitnisse-ruby/180374/3 "2009-12-18T22:59:26Z")

</div>

Thanks, that was close, I had included Test::Unit::TestCase without  
requiring test/unit in my code.Thanks .

Phillip G. wrote:

> On 18.12.2009 19:11, Arti S. wrote:
> 
> > has anyone seen this error before? I have no idea on how to fix I have  
> > all but exhausted myself looking for the solutions to this
> 
> > uninitialized constant Test
> 
> Your suit of tests is lacking a require, somewhere.
> 
> The details depend on what you use for testing, but one option is
> 
> require ‘test/unit’ # Ruby’s included test suit
> 
> That requires should be in every file doing tests, ideally, so you can  
> run them independently.
