Project

Profile

Help

Test #4125

closed

Test if creating duplicate content results in 400

Added by kersom over 5 years ago. Updated almost 5 years ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Version:
Platform Release:
Tags:
Sprint:
Quarter:

Description

  • Evaluate if we already have similar tests in place.
  • Create duplicate content
  • Assert that an HTTP Bad Request - 400 was raised
  • Assert that an error (e.g. "There is already a file content unit with relativepath 'foo.tar.gz' and artifact '/pulp/api/v3/artifacts/1/'.") is returned

Related issues

Related to File Support - Issue #3436: Creating duplicate content results in 500 IntegrityErrorCLOSED - CURRENTRELEASEdaviddavisActions
Copied to Pulp - Test #4975: Docker - Test if creating duplicate content results in 400 CLOSED - DUPLICATEActions
Copied to Ansible Plugin - Test #4976: Collection - Test if creating duplicate content results in 400 CLOSED - WONTFIXActions
Actions #1

Updated by kersom over 5 years ago

  • Related to Issue #3436: Creating duplicate content results in 500 IntegrityError added
Actions #2

Updated by kersom over 5 years ago

  • Assignee set to kersom
Actions #3

Updated by daviddavis over 5 years ago

  • Description updated (diff)
Actions #4

Updated by daviddavis over 5 years ago

This needs to be tested against all plugins (not just pulp_file). To reproduce for other plugins, look at their docs for how to create a content unit and send the same request twice. You should receive a nice 400 + error message.

Actions #5

Updated by kersom over 5 years ago

Added by kersom over 5 years ago

Revision 38e035bb | View on GitHub

Add test to create duplicate content units

Add test to create duplicate content units. They have to share the same artifact and relative_path.

https://pulp.plan.io/issues/4125 ref: #4125

Actions #6

Updated by kersom over 5 years ago

  • Subject changed from Test if creating duplicate content results in 500 to Test if creating duplicate content results in 400
Actions #7

Updated by kersom over 5 years ago

  • Status changed from NEW to ASSIGNED
Actions #8

Updated by dalley over 5 years ago

@David Would it make sense to add this to the "using plugin" section of the pulpcore functional smash tests instead of for each individual plugin?

Added by kersom over 5 years ago

Revision ce395742 | View on GitHub

Expand duplicate content unit test case

Expand newly added duplicate content unit test case. Add a test case to confirm that content units using the same artifact, but different relative_paths can be create without raise an HTTP exception.

https://pulp.plan.io/issues/4125 ref: #4125

Added by kersom over 5 years ago

Revision 721966a0 | View on GitHub

Add test to create duplicate content units

Add test to create content duplicate content units.

https://pulp.plan.io/issues/4125 #4125

Actions #9

Updated by dalley over 5 years ago

Adding a few to the checklist -- you don't have to worry about the plugins QE isn't responsible for, but it would really help us to still track those plugins on the same issue.

Maybe we should add a new status which means that QE has finished with it, but it still needs the non-productized plugin teams to take a look and port the changes to their own codebases.

Actions #10

Updated by kersom over 5 years ago

Actions #11

Updated by bmbouter almost 5 years ago

  • Tags deleted (Pulp 3)
Actions #12

Updated by kersom almost 5 years ago

  • Copied to Test #4975: Docker - Test if creating duplicate content results in 400 added
Actions #13

Updated by kersom almost 5 years ago

  • Copied to Test #4976: Collection - Test if creating duplicate content results in 400 added
Actions #14

Updated by kersom almost 5 years ago

Actions #15

Updated by kersom almost 5 years ago

  • Status changed from ASSIGNED to CLOSED - COMPLETE

Also available in: Atom PDF