Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[12.0][MIG] website_sale_product_attribute_filter_visibility #294

Merged
merged 8 commits into from
Jun 13, 2019
Merged

[12.0][MIG] website_sale_product_attribute_filter_visibility #294

merged 8 commits into from
Jun 13, 2019

Conversation

cor9003
Copy link
Contributor

@cor9003 cor9003 commented May 29, 2019

Migration to 12.0

@pedrobaeza pedrobaeza added this to the 12.0 milestone May 30, 2019
@pedrobaeza
Copy link
Member

Please check Travis and runbot status

@emagdalenaC2i emagdalenaC2i mentioned this pull request Jun 1, 2019
19 tasks
@sergio-teruel
Copy link
Contributor

@cor9003 Is this PR ready for review??
The tour does test nothing....

@cor9003
Copy link
Contributor Author

cor9003 commented Jun 4, 2019

@sergio-teruel This is the fist time I was "fighting" :-) with a testing tour and sorry but do not have experience. I have done several changes but always Mr. travis in red color. I'm sure the module is working fine but the issue for me is the tour, no experience here....

@@ -0,0 +1,9 @@
<?xml version="1.0"?>
<odoo>
<template id="assets_backend" name="tour_attribute_filter" inherit_id="web.assets_backend">
Copy link
Member

Choose a reason for hiding this comment

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

This is not correct. Backend assets are for backend interface testing, and this is not the case.

@@ -22,7 +22,7 @@
<record id="product_attribute_test_size" model="product.attribute">
<field name="website_published" eval="False"/>
<field name="name">Test Size</field>
<field name="create_variant" eval="False"/>
<field name="create_variant">always</field>
Copy link
Member

Choose a reason for hiding this comment

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

Why do you need to change this demo data definition?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

data is not loaded in V12 with eval="False"

Copy link
Member

Choose a reason for hiding this comment

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

But you could use 'none', wich follows the same logic

@@ -6,12 +6,12 @@
class WebsiteSaleHttpCase(HttpCase):

def test_ui_website(self):
"""Test frontend tour."""
"""Test tour."""
Copy link
Member

Choose a reason for hiding this comment

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

It's frontend indeed

@@ -12,5 +12,13 @@
</field>
</field>
</record>

Copy link
Member

Choose a reason for hiding this comment

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

Keep the blank line as it's more readable

@sergio-teruel
Copy link
Contributor

@cor9003 Please squash the commits

@cor9003
Copy link
Contributor Author

cor9003 commented Jun 13, 2019

@sergio-teruel Done 👍

Copy link
Member

@chienandalu chienandalu left a comment

Choose a reason for hiding this comment

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

Thanks for your work!

@pedrobaeza pedrobaeza merged commit ad94a8d into OCA:12.0 Jun 13, 2019
@cor9003
Copy link
Contributor Author

cor9003 commented Jun 13, 2019

@sergio-teruel @chienandalu Sergio, David thanks a lot !

@sergio-teruel
Copy link
Contributor

@cor9003 Ready for other ?? website_sale_product_attribute_value_filter_existing?? 😃

@cor9003
Copy link
Contributor Author

cor9003 commented Jun 13, 2019

@sergio-teruel jajaja of course

@cor9003
Copy link
Contributor Author

cor9003 commented Jun 13, 2019

@sergio-teruel I'm going to start the migration of this module but before I would like to know how to run properly the test of the module website_sale_product_attribute_filter_visibility you did.
I'm using a odoo V12 with --test-enabled and go to Chrome and in console run odoo.DEBUG.services['web_tour.tour'].run('website_sale_product_attribute_filter_visibility', 1000); but I got an error, maybe this is not the way to test.
How can I test your test ?

@sergio-teruel
Copy link
Contributor

Sorry!!, You only need enable the product attribute's filter view and run the tour in web explorer console.

@cor9003
Copy link
Contributor Author

cor9003 commented Jun 27, 2019

@sergio-teruel Sorry, I'm not able to run this test and I think I need to know how run to make successfully the other migration. After enable the product attribute's filter I get the following error: website_sale_product_attribute_filter_visibility failed at step a:contains('Customizable Desk')
And this is becase the attributes Test Color and Test Size has not been created but they are in test_attribute_filter_visibility.py
Maybe is a miss configuration of my server for testing environment or and incorrect procedure I'm doing. I you cannot help me I understand I will continue trying to find a solution to run the test. This is mainly to inform you the delay in other migration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants