Javier Colmenero

Hi, I dont understand new codecov errors. It seems like is detecting lines of code not tested, but in my migration commit i only edit xml files. Is a simple...

Thanks @rousseldenis Yes, tests weren't working, there are references in the test cases that are no longer valid. I will try to fix them throughout the week.

Hi, I need help with a test error. `AssertionError: can't write on invisible field 'quantity' ` It doesn't occur in my local environment with a fresh database. However, I did...

I found that module **contract_variable_qty** is doing: ``` "qty_type != 'fixed'" ``` I don't think the solution is to worry about fields introduced by other modules, especially when the default...

I was trying to understand why the field is invisible in the test, but it doesn’t seem to be.  The invisibility condition is set to False, yet the error...

I tested in local with #1242 and test passed. To pass the test here we need #1243 i think

I did it only to take commits of contract_sale_generation from my PR branch: `git format-patch --keep-subject --stdout origin/18.0..Comunitea/17.0-mig-contract_sale_generation -- contract_sale_generation | git am -3 --keep` But then i realize i...

Hi @pedrobaeza One question that comes to mind after reviewing the procedure is: Since this is for v18, my understanding is that by simply editing the pyproject.toml file within the...

Hi @pedrobaeza To avoid close the PR i try to fix the branch with: `git reset --hard origin/18.0` and doing the `git am` from my PR #1234 branch. Then i...

Hello, I applied the corrections from @acsonefho and removed the test-requirements.txt (since contract_sale has already been merged). I did a rebase, and now the failure is happening in the sale_project...