Valentin Chevalierandxlu-odoo
2d81dffd23
After the payment apocalypse, `payment_test` was cleaned and stripped of all useless parts. It was a very basic testing acquirer that allowed to enter fake arbitrary payment details, choose whether they should be tokenized, and then pay. It was intended to test the payment flow of various applications (Sales, Subscriptions, Invoicing, ...) for a single scenario: successful payments with immediate capture. In order to extensively test an app's payment flow (explore other scenarios), we need `payment_test` to have additional features. Now, `payment_test` will allow profound testing of these features: - separate authorization and capture - customer fees computation - tokenization - refunds - on the /pay page, users will be able to select the status of the payment - on the payment transaction form view, users can change the status of a payment 'pending' to either succeed or fail - on the payment token form view, users can change the state of future transactions made with that token task-2512196 closes odoo/odoo#78083 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> Co-authored-by: xlu-odoo <xlu@odoo.com>
18 lines
661 B
XML
18 lines
661 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
|
|
<record id="payment_token_form" model="ir.ui.view">
|
|
<field name="name">Test Token Form</field>
|
|
<field name="model">payment.token</field>
|
|
<field name="inherit_id" ref="payment.payment_token_form"/>
|
|
<field name="arch" type="xml">
|
|
<group name="general_information" position="inside">
|
|
<field name="provider" invisible="1"/>
|
|
<field name="test_simulated_state"
|
|
attrs="{'invisible': [('provider', '!=', 'test')], 'required': [('provider', '=', 'test')]}"/>
|
|
</group>
|
|
</field>
|
|
</record>
|
|
|
|
</odoo>
|