Let's learn more about the options in the following points:
- Run JS Tests: This option will redirect you to the JavaScript QUnit test case page, as shown in the following screenshot. It will start running all test cases one by one. Here, you can see the progress and the status of the test cases. In Chapter 18, Automated Test Cases, we will see how can we create our own QUnit JavaScript test cases:
- Run JS Mobile Tests: Similar to the preceding option, but this one runs a QUnit test case for a mobile environment.
- Run Click Anywhere Tests: This option will start clicking on all menus one by one. It will click in all the views and search filters. If something is broken or there is any regression, it will show the tracebacks. To stop this test, you will need to reload the page.
- Open View: This option will open a list of all available views. By selecting any of them, you can open that view without defining any menus or actions.
- Start Tour: Odoo uses tours to improve the on-boarding of new users. It also uses tours for automated testing. We will create a custom onpboarding tour in Chapter 16, Web Client Development. This option will open a dialog box with a list of all tours, as shown in the following screenshot. By clicking on the play button next to a tour, Odoo will automatically perform all the steps of the tour:
- Edit Action: In the Adding menu items and views recipe of Chapter 4, Creating Odoo Add-On Modules, we added a menu item and an action to open views in Odoo. Details of these actions are also stored in the database as a record. This option will open the record details of the action we open to display the current view.
- View Fields: This option will help you when you want to see the details of fields from the user interface. It will show a list of fields for the current model. For example, if you open a tree or form view for a library.book model, this option will show a list of fields for the library.book model.
- Manage Filters: In Odoo, users can create custom filters from the search view. This option will open a list of custom filters for the current model. Here, you can modify the custom filters.
- Technical Translations: This option will open a list of translated terms for the current model. You can modify the technical translation terms for your model from here. You can refer to Chapter 12, Internationalization, to learn more about translations.
- Fields View Get: You can extend and modify an existing view from other add-on modules. In some applications, these views are inherited by several add-on modules. Because of this, it is very difficult to get a clear idea of the whole view definition. With this option, you will get the final view definition after applying all view inheritance. Internally, it uses the fields_view_get() method.
- Edit View: <view type>: This option will open the dialog with the ir.ui.view record of the current view. This option is dynamic and it will show an option based on the view that is currently open. This means that if you open the Kanban View, you will get an Edit View: Kanban option, and if you open the Form View, you will get an Edit View: Form option.
You can modify the view definition from the Edit View option. This updated definition will be applicable on the current DB and these changes will be removed when you update the module. It's therefore better to modify views from modules.
- Edit Search View: This option is the same as the preceding one, but it will open the ir.ui.view record of the current model's search view.
- Activate Assets Debugging: Odoo provide two types of developer mode: Developer mode and Developer mode with assets. With this option, you can switch from Developer mode to Developer mode with assets mode. Check the Activating the Odoo developer tools recipe of Chapter 1, Installing the Odoo Development Environment, for more details.
- Regenerate Assets Bundles: Odoo manages all CSS and JavaScript through assets bundles. This option deletes the old JavaScript and CSS assets and generates new ones. This option is helpful when you are getting issues because of asset caching. We will learn more about assets bundles in Chapter 12, CMS Website Development.
- Become Super User: This is a new option in version 12. By activating this option, you switch to a super user. You can access the records even if you don't have access rights. This option is not available for all users; it is only available for users who have Administration: settings access rights. After activating this mode, you will see a striped top menu, as shown here:
- Leave Developer Tools: This option allows you to leave developer mode.