How to test odoo modules - odoo

I developed an odoo module, I want to test it, I alreay read this topic testing odoo module, but there is no enought details about this.

Actually you are trying to test your module but the link you provide is for creating python test cases. I think this might help you.

Related

Best practices writing Espresso tests for a multi modular Android projects (MVI/MVVM)

I am looking into Espresso Framework to adopt the best practices for writing tests for a multi modular Android projects (MVI/MVVM).
Is it a good idea to cover/write all the Espresso tests inside the app module (or) it needs to be isolated specific to each modules?
Is there any other best practices for MVI/MVVM based Android projects? if so, please comment and provide references if any
Language used: Kotlin
I have recently been implementing espresso tests in the multi-modular project where I work. Through some research and help from senior developers, I think I will be able to guide you a bit in the proper direction.
For the first question, Yes, it's essential that all the tests related to a particular activity remain in their corresponding 'test' class. That keeps it modular and easy to debug. So, one should make a test class for a particular activity and that should be in the corresponding module that the 'activity' belongs.
All these test classes can then help you to build a 'TestSuite' which could be used to make a flow for testing the app's specific features. In a test suite, one needs to mention those classes that make that flow.
After all this research and as per knowledge, I guess, this approach is good enough for large projects as well since the app I am working on is really big.
Blocker :
In a multi-modular project, I am still not able to create the test suite since I am not able to import those test classes in the main app module. But this issue will be fixed very soon. I'll definitely update it here when I'll get the method to do so.
Please do comment, if I am doing something wrong. Suggestions are a warm welcome.

Migration from 0.9.5 to 1.0.1 - ScriptBridge class equivalent

We would like to move our api test created using karate framework to karate framework 1.0.1. I see that there is no such class as ScriptBridge which is used by us to attach screenshots and get information about test status, tags of currently running scenario.
What is the equivalent for the ScriptBridge class?
My question is related with Attaching screenshots to json report where I asked how to attach screenshots to report.
Short answer to your question, the class you are looking for is ScenarioBridge.
But the HTML reporting has been overhauled and hopefully you will be able to achieve what you need without hacking into internal classes. There is a somewhat undocumented doc keyword, you will find an example in the link below. If you feel helpers for handling images need to be part of Karate, do contribute or suggest a feature request.
Please read this: https://stackoverflow.com/a/66822585/143475

Has anyone figured out how to program the STWBC-MC module by STM?

The documents say that we can flash custom firmware on this module but it doesn't say how. I am unable to locate any build tool chain either. I tried raising a customer support ticket with STM and they don't seem to have any answers. Has anyone used this module in any of their products?
The User Manual for the STMWB-CM evaluation kit explains the programming process (see section 3.6). You use an ST-LINK/V2 in-circuit debugger/programmer with single wire interface module (SWIM) and STVP software.
It is STM8 and you need IAR workbench for it. I believe that you need to sign NDA first, then (when accepted) you get more detailed documentation and libraries.
Contact you STM FAE for more details.

Need to create a Vtiger 6.1 custom module

I need to create a Vtiger 6.1 custom module, that will be in relation with Organisation module, with list view on Organisation details page.
I couldn't find any documentation for such situation, all I found was a basic custom module structure with very limited and standalone functionality.
Can anyone suggest anything please.
Thank you in advance.
You can use Module Designer for making custom module.
Below link helps you to create custom module.
https://www.youtube.com/watch?v=PF3noyh7M-g

Easy acceptance testing with specification

I look for a tool/framework to make automatic acceptance-testing. The interface to create new tests should be so easy, that a non-programmer (customer, boss) will be able to add specifications for which will be tested automatically.
It should be some way to execute the tests from command-line, to include a run of the tests in automatic builds.
I prefer Java and Open-Source, but my question isn't restricted in that way.
What do you can recommend and please explain why your tool/framework is the best in the world.
http://fitnesse.org/ appears to meet all of the qualifications you want. It is one I have used with success.
I think that several of the options are very good and you should test them to see which fits your team :
Cucumber (Ruby)
Fitnesse
Robot framework (Python/Java)
Behave for Java
SpecFlow (.net)
Another framework you may want to look at is Robot Framework. To see how test cases look like, take a look at the Quick Start Guide.
I've found a framework named Concordion that may fulfill my needs.
What you ask for appears to be for a very well-defined system with a very specific sets of inputs and a high degree of automation built-into the system or developed for your system.
Commercial applications such as HP Quick Test Pro isn't non-technical enough and requires an additional framework such as one from Sonnet, which is a step in the right direction, but neither is open source or java-based.
Even with a framework in place, it's quite a bit of work to make this work in an automated way. I'd like you to consider the time needed to develop the framework vs the time to manually run these tests and verify that you are using your time well.
How about Cucumber:
Feature: Acceptance testing framework
Scenario: an example speaks volumes
Given a text example
When it is read
Then the simplicity will be appreciated
You would need a developer to discuss with the boss what each of those lines really means and implement the step definition to drive it:
Given /^a text example$/ do
file.open("example.txt", "w") { |file| file.write "text example" }
end
When /^it is read$/ do
SystemUnderTest.read("example.txt")
end
Then /^the simplicity will be appreciated$/ do
SystemUnderTest.simplicity.should be_appreciated
end