Skip to content

[16.0][IMP] dms_field: Add partner embedded DMS template#378

Merged
OCA-git-bot merged 1 commit into
OCA:16.0from
Tecnativa:16.0-imp-dms_field-issue-377
Nov 25, 2024
Merged

[16.0][IMP] dms_field: Add partner embedded DMS template#378
OCA-git-bot merged 1 commit into
OCA:16.0from
Tecnativa:16.0-imp-dms_field-issue-377

Conversation

@victoralmau

@victoralmau victoralmau commented Nov 19, 2024

Copy link
Copy Markdown
Member

Add partner embedded DMS template

Fixes #377

Please @pedrobaeza and @CarlosRoca13 can you review it?

@Tecnativa

@pedrobaeza

Copy link
Copy Markdown
Member

We should avoid using demo data on tests.

@victoralmau victoralmau force-pushed the 16.0-imp-dms_field-issue-377 branch 2 times, most recently from be9b288 to 1b78a1d Compare November 19, 2024 09:32
@victoralmau

Copy link
Copy Markdown
Member Author

We should avoid using demo data on tests.

I don't totally agree, but ok, it's already changed.

@victoralmau

Copy link
Copy Markdown
Member Author

Ping @pedrobaeza

@pedrobaeza pedrobaeza added this to the 16.0 milestone Nov 25, 2024

@pedrobaeza pedrobaeza left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should avoid using demo data on tests.

I don't totally agree, but ok, it's already changed.

About this, the reasons are:

  • Being self-contained: any change on data across versions/updates that affect the tests are not contained on the test file itself, and they are more difficult to be traced.
  • Being reliable: if you depend on demo data, that demo data may be manually altered on the current DB, making the test to fail.

Thus, we must avoid it, the same as finally Odoo has done in its own tests.

In this module, I also see more dependencies to demo data (like dms.access_group_01_demo, dms.storage_demo, etc), so they must be removed.

Comment thread dms_field/tests/test_dms_field.py Outdated
@victoralmau victoralmau force-pushed the 16.0-imp-dms_field-issue-377 branch from 1b78a1d to 0b6c950 Compare November 25, 2024 16:53

@pedrobaeza pedrobaeza left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/ocabot merge patch

@OCA-git-bot

Copy link
Copy Markdown
Contributor

This PR looks fantastic, let's merge it!
Prepared branch 16.0-ocabot-merge-pr-378-by-pedrobaeza-bump-patch, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit 9094d39 into OCA:16.0 Nov 25, 2024
@OCA-git-bot

Copy link
Copy Markdown
Contributor

Congratulations, your PR was merged at 1670f54. Thanks a lot for contributing to OCA. ❤️

@pedrobaeza pedrobaeza deleted the 16.0-imp-dms_field-issue-377 branch November 25, 2024 20:54
victoralmau added a commit to Tecnativa/dms that referenced this pull request Nov 29, 2024
We need to avoid applying a template except when testing functionality
with dms_field* modules to avoid the error that a directory with the same
name already exists (example: create partner).

Related to OCA#378
victoralmau added a commit to Tecnativa/dms that referenced this pull request Nov 29, 2024
We need to avoid applying a template except when testing functionality
with dms_field* modules to avoid the error that a directory with the same
name already exists (example: create partner).

Related to OCA#378
CarlosRoca13 pushed a commit to Tecnativa/dms that referenced this pull request Apr 29, 2025
We need to avoid applying a template except when testing functionality
with dms_field* modules to avoid the error that a directory with the same
name already exists (example: create partner).

Related to OCA#378
CarlosRoca13 pushed a commit to Tecnativa/dms that referenced this pull request Apr 29, 2025
We need to avoid applying a template except when testing functionality
with dms_field* modules to avoid the error that a directory with the same
name already exists (example: create partner).

Related to OCA#378
luisDIXMIT pushed a commit to dixmit/dms that referenced this pull request May 9, 2025
We need to avoid applying a template except when testing functionality
with dms_field* modules to avoid the error that a directory with the same
name already exists (example: create partner).

Related to OCA#378
victoralmau added a commit to Tecnativa/dms that referenced this pull request May 12, 2025
We need to avoid applying a template except when testing functionality
with dms_field* modules to avoid the error that a directory with the same
name already exists (example: create partner).

Related to OCA#378
victoralmau added a commit to Tecnativa/dms that referenced this pull request May 12, 2025
We need to avoid applying a template except when testing functionality
with dms_field* modules to avoid the error that a directory with the same
name already exists (example: create partner).

Related to OCA#378

[BOT] post-merge updates
victoralmau added a commit to Tecnativa/dms that referenced this pull request May 12, 2025
We need to avoid applying a template except when testing functionality
with dms_field* modules to avoid the error that a directory with the same
name already exists (example: create partner).

Related to OCA#378
victoralmau added a commit to Tecnativa/dms that referenced this pull request May 12, 2025
We need to avoid applying a template except when testing functionality
with dms_field* modules to avoid the error that a directory with the same
name already exists (example: create partner).

Related to OCA#378

[BOT] post-merge updates
victoralmau added a commit to Tecnativa/dms that referenced this pull request May 13, 2025
We need to avoid applying a template except when testing functionality
with dms_field* modules to avoid the error that a directory with the same
name already exists (example: create partner).

Related to OCA#378

[BOT] post-merge updates
victoralmau added a commit to Tecnativa/dms that referenced this pull request May 14, 2025
We need to avoid applying a template except when testing functionality
with dms_field* modules to avoid the error that a directory with the same
name already exists (example: create partner).

Related to OCA#378

[BOT] post-merge updates
victoralmau added a commit to Tecnativa/dms that referenced this pull request Jun 24, 2025
We need to avoid applying a template except when testing functionality
with dms_field* modules to avoid the error that a directory with the same
name already exists (example: create partner).

Related to OCA#378

[BOT] post-merge updates
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants