Question

我编写了一个注册表单的集成测试，该表单写入两个表/模型。它失败并显示消息"Organization.count" didn't change by 1。但是，是否有一种方法可以查看测试失败的错误消息（表单在开发中有效，尽管显示错误消息存在问题，因此我不明白测试失败的原因）。所以我的意思是如果你在服务器上做了同样的事情，那么你会看到的错误信息可以帮助我找出它为什么没有保存组织/用户。

  test "valid combined organization user signup" do
    get new_path
    assert_template 'organizations/new'
    assert_difference ['Organization.count', 'User.count'], 1 do
      post organizations_path, organization: { name: "Abc1",
                                               bag: "aef1",
                            users_attributes: [email: "test@test.br",
                                               username: "abc1",
                                               password: "foobar",
                                               password_confirmation: "foobar"] }
       end
  end

也许测试日志可以帮忙吗？我在这里看到IS NULL LIMIT用户的电子邮件和用户名。鉴于测试语法，我不明白为什么......

Started POST "/organizations" 
Processing by OrganizationsController#create as HTML
  Parameters: {"organization"=>{"name"=>"Abc def 1", "bag"=>"adef1", "users_attributes"=>[{"email"=>"adef1@uniqu.br", "username"=>"adef1", "password"=>"[FILTERED]", "password_confirmation"=>"[FILTERED]"}]}}
  [1m[36m (0.2ms)[0m  [1mSAVEPOINT active_record_1[0m
  [1m[35mOrganization Exists (0.6ms)[0m  SELECT  1 AS one FROM "organizations" WHERE LOWER("organizations"."name") = LOWER('Abc def 1') LIMIT 1
  [1m[36mOrganization Exists (0.3ms)[0m  [1mSELECT  1 AS one FROM "organizations" WHERE LOWER("organizations"."bag") = LOWER('adef1') LIMIT 1[0m
  [1m[35mOrganization Exists (0.3ms)[0m  SELECT  1 AS one FROM "organizations" WHERE LOWER("organizations"."name") = LOWER('Abc def 1') LIMIT 1
  [1m[36mOrganization Exists (0.3ms)[0m  [1mSELECT  1 AS one FROM "organizations" WHERE LOWER("organizations"."bag") = LOWER('adef1') LIMIT 1[0m
  [1m[35mSQL (0.4ms)[0m  INSERT INTO "organizations" ("name", "bag", "created_at", "updated_at") VALUES ($1, $2, $3, $4) RETURNING "id"  [["name", "Abc def 1"], ["bag", "adef1"], ["created_at", "2015-06-27 16:28:56.179789"], ["updated_at", "2015-06-27 16:28:56.179789"]]
  [1m[36mUser Exists (0.6ms)[0m  [1mSELECT  1 AS one FROM "users" WHERE "users"."email" IS NULL LIMIT 1[0m
  [1m[35m (0.6ms)[0m  SELECT "users"."email" FROM "users"  ORDER BY "users"."username" ASC
  [1m[36mUser Exists (0.2ms)[0m  [1mSELECT  1 AS one FROM "users" WHERE "users"."username" IS NULL LIMIT 1[0m
  [1m[35m (0.2ms)[0m  ROLLBACK TO SAVEPOINT active_record_1

控制器方法发布在此处：stackoverflow.com/q/31072646/4499505（organizations_path指的是创建方法）

如果我将测试日志与开发日志进行比较（因为在开发过程中表单确实有效），对于开发，它会在下面发布，这似乎与测试日志中的帖子不同。我应该如何调整测试语法以创建与开发中相同的帖子？

Parameters: {"utf8"=>"✓", "authenticity_token"=>"***", "organization"=>{"name"=>"test60", "bag"=>"tes60", "users_attributes"=>{"0"=>{"email"=>"test60@example.com", "username"=>"test60", "password"=>"[FILTERED]", "password_confirmation"=>"[FILTERED]"}}}, "commit"=>"Register"}

更新：为了匹配开发日志，我将测试中的post行更改为：

post organizations_path, organization: { name: "Abc def 1",
                                         bag: "adef1",
             users_attributes: { "0" => {email: "adef1@uniqu.br",
                                         username: "adef1",
                                         password: "foobar",
                                         password_confirmation: "foobar"}} }
end

现在在测试日志中它不再有IS NULL LIMIT但它仍然会回滚，因此测试仍然会失败并显示相同的消息：

  [1m[35mSQL (0.5ms)[0m  INSERT INTO "organizations" ("name", "bag", "created_at", "updated_at") VALUES ($1, $2, $3, $4) RETURNING "id"  [["name", "Abc def 1"], ["bag", "adef1"], ["created_at", "2015-06-27 19:49:45.430750"], ["updated_at", "2015-06-27 19:49:45.430750"]]
  [1m[36mUser Exists (0.4ms)[0m  [1mSELECT  1 AS one FROM "users" WHERE LOWER("users"."email") = LOWER('adef1@uniqu.br') LIMIT 1[0m
  [1m[35m (0.5ms)[0m  SELECT "users"."email" FROM "users"  ORDER BY "users"."username" ASC
  [1m[36mUser Exists (0.5ms)[0m  [1mSELECT  1 AS one FROM "users" WHERE LOWER("users"."username") = LOWER('adef1') LIMIT 1[0m
  [1m[35m (0.2ms)[0m  ROLLBACK TO SAVEPOINT active_record_1

Answer 1

您的测试代码与开发代码的作用不同。您需要在users_attributes数组中添加括号：

test "valid combined organization user signup" do
  get new_path
  assert_template 'organizations/new'
  assert_difference ['Organization.count', 'User.count'], 1 do
    post organizations_path, 
         organization: { name: "Abc1",
                         bag: "aef1",
                         users_attributes: { "0" => { email: "test@test.br",
                                                      username: "abc1",
                                                      password: "foobar",
                                                      password_confirmation: "foobar" } } }
  end
end

这就是为什么您的日志说它正在尝试找到email IS NULL的用户，因为它无法正确检索email属性，所以它只是默认为NULL而不是test@test.br。

修改更新以匹配工作语法。 OP还报告说，一旦语法修复，User模型没有通过username上的最小长度验证就会出错，他只需在测试数据中使用较长的用户名即可修复。 / p>

为什么此次集成测试与发布请求失败？

1 个答案: