Automated testing tools available for odoo - testing

Is there any automated tool available for ODOO? Also, how does the YML File Structure work to use builtin add-ons in ODOO.

Check runbot in https://github.com/odoo/odoo-extra repo.
This repository contains the source code of Odoo testing bot runbot.odoo.com. Please have a look in the runbot/ directory.
It may be help you.

The Odoo Community Association uses TravisCI to perform tests on each build of their projects. The tooling that makes that possible is the Maintainer Quality Tools project, and is suitable to be used in your own Odoo projects.

Related

How I can make the URL of my summary report public to share in Karate framework [duplicate]

I'm trying to get reporting working for Karate DSL, and it's proven a challenge because my team uses Circle CI instead of Jenkins. Cucumber reporting seems to only work for Jenkins.
I've had a look at this documentation, here:
https://github.com/intuit/karate/tree/master/karate-demo#example-report
https://github.com/jenkinsci/cucumber-reports-plugin
I was wondering if there is a circle friendly equivalent you could recommend? It'd be even better if the reports could be generated in the terminal. It's going to be a hard sell to convince my team to change CI tools just so I can implement a test framework.
Thanks!
Here's what I suggest:
If you follow the demo / doc instructions - you will get the HTML reports in say target/cucumber-html-reports, and this is "pure Maven and Java", no dependency on CircleCI at all so far.
Now all you need to do is somehow make these HTML reports accessible via the web. In Jenkins, there is an HTML Publisher Plugin. I am not familiar with CircleCI but a quick search suggests that there is a way to expose links to build artifacts.
Also note that when you follow the demo, Java JUnit XML reports would also be output to target/cucumber-reports. It looks like CircleCI has support for these which means that it should be able to derive the build pass/fail status and stats if configured right.
Also note that Karate now enables you to write custom reports: https://stackoverflow.com/a/66773839/143475

How to do Automation Testing on Openerp or Odoo?

I want to test odoo modules with the help of Automation Testing Tools.
How can i do that, pls give me suggestion.
Is there any automation testing tool available for odoo project testing?
Thanks in advance.
**You can use selenium testing tool & write a script in it
Also u can do YML testing by writing YML script in test files of an OpenERP or ODOO
**
https://doc.odoo.com/6.0/developer/5_16_data_serialization/yaml_serialization/
You can try open source tools like Selenium.
Additionally, I found this slideshare presentation,
http://www.slideshare.net/openobject/how-to-develop-automated-tests
...which talks about run-bot.

Openlaszlo in Eclipse

Can anybody tell me how to add the openlaszlo plugin to the eclipse or any IDE for openlaszlo ?
Thank you!
IDE4Laszlo - http://wiki.openlaszlo.org/IDE4Laszlo - an Eclipse-based development environment for creating, editing, debugging, and testing applications based on the LZX declarative mark-up language.
Also check https://stackoverflow.com/a/11676129/363075 for details of other development tools for OpenLaszlo.
I would use the Spket IDE plugin. It has some support for Laszlo, and I've used it in projects. The old IBM IDE project has been discontinued back in 2006. The Eclipse Update Site for Spket is http://www.agpad.com/update.
If you would rather use an XML Schema file with Eclipse, there is an Ant build script capable of generating a custom XSD file for your application. See the OpenLaszlo Schema Generator site for more info.

How to write an IntelliJ IDEA Plugin?

IDEA has many plugins to use. I.e. IDEtalk is one of them which I use. How can I code a simple plugin that just connects to Internet and shows a web page? (no need for an address bar but it is not a problem to be). I want my plugin's shortcut's button locate at my IDE as like IDEtalk, Commander, Maven Projects etc.
Any ideas?
Check the documentation and the source code of the other plug-ins available in the public git repository of the Community Edition.
There is a Creating Your First Plugin guide on JetBrains web site. It covers all the needed steps from plugin creation to deployment to the plugin repository.
You might also want take a look in the source code of a simple plugin like Twitter Integration Plugin which I recently implemented. Or check a more complex one like this one.

Difference between feature and plugin.xml?

I have some basic questions in eclipse plugin development, can anyone give clarification of the following questions,
When should we have to add features in our plugin development ?
What is the difference between feature and plugin.xml ?
Regards
Mathan
As mentioned in this thread:
A plugin is the eclipse "unit of work". An OSGi bundle that supplies a classpath and can contribute to eclipse through extensions.
A fragment points to a host plugin, and anything it provides (classpath, extensions, etc) are "sucked" into the host plugin. A fragment is also a more specialized OSGi bundle.
A feature represents a versioned collection of plugins, and is used for configuration management in eclipse. They can be deployed manually or through the update manager. If you want to deploy through the update manager, then you need to use features to represent your plugins.
So if you want to manage your plugin or plugins through the update manager, a feature is in order.
You can find more in the Eclipse Help:
Feature
Features do not contain any code.
They merely describe a set of plug-ins that provide the function for the feature and information about how to update it.
Features are packaged in a feature archive file and described using a feature manifest file, feature.xml.
Plugin
While features are organized for the purposes of distributing and updating products, plug-ins are organized to facilitate the development of the product function among the product team. The development team determines when to carve up program function into a separate plug-in.
Plug-ins are packaged in a plug-in archive file and described using a plug-in manifest file, plugin.xml.