86 Commits (eae789855a2f5d242901e69679f6f7f78aeaedd0)

Author	SHA1	Message	Date
Richard	52e671500b	Stole Hagen's fix for db transaction issue.	11 years ago
Johannes Wollert	8b096975fe	updates copyright headers ... updates more copyright more copyright headers	11 years ago
Philipp Tessenow	90ddb7a797	remove accidentaly commited line from spec_helper	11 years ago
Philipp Tessenow	ce68fdf70b	add fancy collection_select helper in the tabular_form_helper	11 years ago
Philipp Tessenow	90f0f21cbb	try to enable code climate	11 years ago
Philipp Tessenow	ef98734abd	send coverage reports to code climate when running on a CI server	11 years ago
Stefan Frank	e731281d36	Added a spec for the json-response of the api	11 years ago
Philipp Tessenow	a1e67dd460	new copyright header #1903	11 years ago
Martin Czuchra	daa4ee953c	Removes more occurances of Issue constant.	11 years ago
Michael Frister	02e51b520a	Remove coveralls for now, seems to be broken for months.	11 years ago
Michael Frister	11792d4972	Run coverage reporting only on Travis	11 years ago
Jens Ulferts	a47e672bb2	no longer warns against a lazy spec implementation if AnonymousUser is set	11 years ago
Michael Frister	9f615317da	Reduce number of warnings for specs that don't reset User.current ... Don't show the warning if User.current is an AnonymousUser. Any access to User.current sets the current user to an AnonymousUser, so without this change, the warning about User.current not being reset is issued falsely for any test that runs code accessing User.current. While it probably is a good idea to remove User.current everywhere, issuing way too many warnings during specs won't accomplish this.	11 years ago
Jens Ulferts	da192e4e95	removes unused require	12 years ago
Jens Ulferts	dadcda2c15	less verbose warnings, especially on the second run	12 years ago
Jens Ulferts	8059055b5b	ensures cleaning up User.current after each step ... When User.current is set by a spec, an instance variable of the class gets set to the provided value. This instance variable is not reset between specs to the next spec will "profit" as well. This commit implements cleaning up after such lazy specs. The lazy specs should be improved so that this cleanup is no longer required. However I do not have the time to do this right now. As a reminder I implemented a very verbose warning which should give us enough of an encouragement that we will improve the specs eventually.	12 years ago
Jens Ulferts	21459a384f	provide every possible file with a short copyright notice ... This was done using the rake task: rake copyright:update	12 years ago
Philipp Tessenow	49c4506162	added SimpleCov OpenProject profile	12 years ago
Philipp Tessenow	8643925b8a	lets push coverage data to coveralls when all tests pass	12 years ago
Michael Frister	2f8c44916d	Allow plugins to disable core specs via rspec-example_disabler ... Plugins can create a spec/disable_specs.rb and call RSpec::ExampleDisabler.disable_example from there.	12 years ago
Christian Rijke	dee98037a6	Remove even more spork stuff.	12 years ago
Christian Rijke	70b5a9b5cb	Remove even more spork stuff.	12 years ago
Philipp Tessenow	fd939f6dbb	Remove spork. Most likely it causes the pry segfaults. Plus you may use Zeus, which does not need any entry in Gemfile or spec_helper.rb	12 years ago
Christian Ratz	bd779b4f82	enable testing plugins from OpenProject core ... - created rake task to run plugin specs - added config variable where plugins can register for tests - added after(:suite) block in spec_helper to check for wrong used before(:all)	12 years ago
Philipp Tessenow	afb19d0974	no more rspec warnings	12 years ago
Martin Linkhorst	88fda30a3b	ran spec install generator	12 years ago
Martin Linkhorst	c50edb6f99	optimize the spec helper for spork	12 years ago
Martin Linkhorst	d580d6054b	added spork to the mix	12 years ago
Martin Linkhorst	ff21667caf	added guard for rspec	12 years ago
Martin Linkhorst	58febd3880	add rspec and capybara stubs	12 years ago