プロジェクト

全般

プロフィール

Vote #81043

未完了

Add missing fixtures to IssueNestedSetTest

Admin Redmine さんが約2年前に追加. 約2年前に更新.

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Code cleanup/refactoring_30
対象バージョン:
-
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
30
version_id:
0
issue_org_id:
33938
author_id:
362529
assigned_to_id:
0
comments:
3
status_id:
1
tracker_id:
3
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

Sometimes IssueNestedSetTest fails.


$ RAILS_ENV=test bundle exec rake db:migrate:reset

$ RAILS_ENV=test bundle exec rake test
Run options: --seed 43474

Running:

............F

Failure:
IssueNestedSetTest#test_destroy_should_destroy_children [./test/unit/issue_nested_set_test.rb:225]:
"JournalDetail.count" didn't change by -1.
Expected: 7
Actual: 6

bin/rails test test/unit/issue_nested_set_test.rb:216

.........F

Failure:
IssueNestedSetTest#test_destroy_child_issue_with_children [./test/unit/issue_nested_set_test.rb:270]:
"JournalDetail.count" didn't change by -1.
Expected: 7
Actual: 6

bin/rails test test/unit/issue_nested_set_test.rb:262

........

Finished in 410.935528s, 12.2404 runs/s, 56.5588 assertions/s.
5030 runs, 23242 assertions, 2 failures, 0 errors, 3 skips

You have skipped tests. Run with --verbose for details.
$


journals

I think that because of the fixtures are not enough.

<pre><code class="diff">
diff --git a/test/unit/issue_nested_set_test.rb b/test/unit/issue_nested_set_test.rb
index 3c6f46adf..c79ff48cc 100644
--- a/test/unit/issue_nested_set_test.rb
+++ b/test/unit/issue_nested_set_test.rb
@@ -24,7 +24,7 @@ class IssueNestedSetTest < ActiveSupport::TestCase
:trackers, :projects_trackers,
:issue_statuses, :issue_categories, :issue_relations,
:enumerations,
- :issues
+ :issues, :journals, :journal_details

def setup
User.current = nil
</code></pre>
--------------------------------------------------------------------------------
I cannot reproduce the problem.

<pre>
$ RAILS_ENV=test bin/rake db:reset
$ ruby test/unit/issue_nested_set_test.rb
Run options: --seed 59495

# Running:

.......................

Finished in 7.030327s, 3.2715 runs/s, 8.9612 assertions/s.
23 runs, 63 assertions, 0 failures, 0 errors, 0 skips

</pre>
--------------------------------------------------------------------------------
Go MAEDA wrote:
> I cannot reproduce the problem.
>
> [...]

You can reproduce it by testing as follows. I think it's because of the order in which the tests are run.

<pre>
$ RAILS_ENV=test bundle exec rake db:migrate:reset

$ RAILS_ENV=test bundle exec rake test TESTOPTS="--seed 43474"
Run options: --seed 43474

# Running:

....F

Failure:
IssueNestedSetTest#test_destroy_should_destroy_children [/Users/harada/_work_/redmine/git/dev-trunk/test/unit/issue_nested_set_test.rb:225]:
"JournalDetail.count" didn't change by -1.
Expected: 7
Actual: 6

bin/rails test test/unit/issue_nested_set_test.rb:216

..........F

Failure:
IssueNestedSetTest#test_destroy_child_issue_with_children [/Users/harada/_work_/redmine/git/dev-trunk/test/unit/issue_nested_set_test.rb:270]:
"JournalDetail.count" didn't change by -1.
Expected: 7
Actual: 6

bin/rails test test/unit/issue_nested_set_test.rb:262

.............

Finished in 405.463254s, 12.4031 runs/s, 57.2555 assertions/s.
5029 runs, 23215 assertions, 2 failures, 0 errors, 7 skips
</pre>
--------------------------------------------------------------------------------

Admin Redmine さんが約2年前に更新

  • カテゴリCode cleanup/refactoring_30 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0