In this chapter, we will cover the following recipes:
When it comes to developing large applications, automated test cases are a good practice for improving the reliability of your module. This makes your module more robust. Every year, Odoo releases a new version of its software, and automated test cases are very helpful in detecting regression in your application, which may have been generated due to a version upgrade. Luckily, an Odoo framework comes with different automated testing utilities. Odoo includes the following three main types of tests:
In this chapter, we will look at all of these test cases in detail. In order to cover all of test cases in the same module, we have created a small module....
The technical requirements for this chapter include the online Odoo platform.
All the code used in this chapter can be downloaded from the GitHub repository, at https://github.com/PacktPublishing/Odoo-12-Development-Cookbook-Third-Edition/tree/master/Chapter18.
Check out the following video to see the Code in Action: http://bit.ly/2UCzjBT
Python test cases are used to check the correctness of the business logic. In Chapter 6, Basic Server-Side Development, you saw how you can modify the business logic of the existing app. This makes it even more important, as customization might break the app's functionality. In this chapter, we will write a test case to validate the business logic to change the book's state.
We will be using the my_library module from the Chapter18/r0_initial_module directory of the GitHub repository.
Follow these steps to add Python...
When you run the Odoo server with the --test-enabled module, the test cases run immediately after the module is installed. If you want to run a test case after the installation of all the modules, or if you just want to run a test case for only one module, a tagged() decorator is the answer. In this recipe, we will illustrate how to use this decorator to mold test cases.
For this recipe, we will be using the my_library module from the last recipe. We will modify the sequence of the test case.
Add a tagged...
Odoo v12 uses Headless Chrome for performing JavaScript test cases and tour test cases. In this recipe, we will install Headless Chrome and other packages, in order to run JavaScript test cases.
You will need to install a Chrome browser to enable a JavaScript test case. For the development of the modules, we mostly use the desktop OS. Consequently, if you have a Chrome browser installed in your system, then there is no need to install it separately. You can run client-side test cases with desktop Chrome itself. Make sure that you have a Chrome version higher than Chrome 59. Odoo also supports the Chromium browser.
Building new fields or views is very simple in Odoo. In just a few lines of XML, you can define a new view. However, under the hood, it uses JavaScript in large amounts. Modifying/adding new features on the client side is complex, and it might break a few things. Most of the client-side issues go unnoticed, as most errors are only displayed in the console. So, QUnit test cases are used in Odoo to check the correctness of different JavaScript components.
For this recipe, we will continue using the my_library module from the previous recipe. We will add a QUnit test case for the int_color widget.
You have now seen Python and JavaScript test cases. Both of these work in an isolated environment, and they don't interact with each other. To test integration between JavaScript and Python code, tour test cases are used.
For this recipe, we will continue using the my_library module from the previous recipe. We will add a tour test case to check the flow of the book model.
Follow these steps to add a tour test case for books:
odoo.define(...
Odoo provides a way to run client-side test cases from the UI. This helps you to see the status of each test case from the user interface.
You can run both the QUnit test case and the tours test case from the UI. It is not possible to run Python test cases from the UI. In order to see the options to run test cases from the UI, you need to enable developer mode.
Click on the bug icon to open the drop-down menu, as shown in the following image. Click on the Run JS Tests option:
This will...
Developing complex client-side test cases can be a headache. In this recipe, you will learn how you can debug the client-side test cases in Odoo. Instead of running all of the test cases, we will just run the single one. Additionally, we will display the UI of the test case.
For this recipe, we will continue using the my_library module from the previous recipe.
Follow these steps to run the test case in debug mode:
Odoo version 11 uses PhantomJS to run the test cases on the server side, but Odoo 12 uses Headless Chrome. This opens new possibilities. With Odoo 12, you can record videos of the failed test cases, or you can take screenshots of the failed test cases.
Recording a video for the test case requires an ffmpeg package. To install this, you need to execute the following command in the Terminal (note that this command only works on a Debian-based OS):
apt-get install ffmpeg
Generating a video or screenshot requires the directory location of the log file, so if you are not saving the log in a separate log file, then do it through the --logfile option in the command...
© 2019 Packt Publishing Limited All Rights Reserved
