Hi all,
The 2025 v13 Community Testing Days are almost here - taking place next Tuesday & Wednesday (Nov 25-26)!
To
help you get ready, we’ve published a detailed blog post covering
everything you need to know to start testing effectively, even if this
is your first time contributing:
https://idempiere.org/blog/2025/11/22/testing-day-kick-off-guide/
Key info from the post:
Choose your preferred environment: PostgreSQL (test.idempiere.org), Oracle (test-oracle.idempiere.org), or the feature environment (https://test-feature.idempiere.org:3243/webui/).
You can test the REST API from Postman to test.idempiere.org.
Request edit access to our collaborative test cases document here:
https://docs.google.com/document/d/1ehGAJW4mvqKWO6scsngpSuhVo6eknarY6uHO6yueR5I/edit?usp=sharing
Join the #triage Mattermost channel to coordinate, ask questions, and report issues in real time.
Test anytime during the two-day event; no need to commit full days.
We strongly encourage everyone: experienced testers and first-timers alike to participate. Your feedback is crucial to delivering a rock-solid iDempiere v13 release.
Get started today: Request edit access to the document and join #triage to say hello!
Looking forward to your contributions! 🚀
Diego Ruiz
What’s New and Important to Test in iDempiere v13
As we gear up for community testing days, here’s an overview of key new features and improvements. Many improvements from the NF12 cycle were included after the release, so testing them now will still help increase stability and quality!
Selected NF12 Features (Worth Testing!):
Context Variable HTML Report Theme and Theme Customization: Improved UI flexibility for reports and layouts.
Exclude Charges From Payment Discount and Multiple Payments Against Statement Line: Important enhancements in payment processing.
New Fields in Country & Prepay Order Configurable Shipment and Invoicing: Core functional improvements in business processes.
Reactivation of Invoices, Support UOM On Inventory Move, and Unallocated Cash & Payment Selection Configurable Business Partner: Critical fixes and features to improve inventory and financial workflows.
And many more detailed features related to password hashing, email templates, document search layout, export definitions, SSO, and plugin extensions. See the full list here for details: NF12 Feature Wiki Category
Accounting Schema Valid Range and New Accounting Dimensions: Enhancements to financial configuration.
Approval Column on Workflow Node, Override Workflow Responsible, and multiple workflow node improvements: Streamlined approval and task management.
Custom Key of Document Sequence and Advanced Options for Saved Queries: Better control over documents and queries.
And much more listed in the NF13 wiki category: NF13 Feature Wiki Category
These features represent months of development by our core team and contributors like you.
Your testing helps:
Confirm new functionality works as expected in your environments
Discover edge cases or unexpected behaviors
Provide vital feedback to improve workflows, reports, and integration points
Protect the stability of the release for all users
Focus on modules related to your expertise or interest
Challenge the features beyond “happy path” scenarios - think about complex, real-world usage
Pair with others or ask questions in #triage if you get stuck
Use the test cases document to guide your tests or add new cases if you find gaps
Get familiar with the features today and come ready to test starting Tuesday!
For all details on how to get started, see the full blog post: https://idempiere.org/blog/2025/11/22/testing-day-kick-off-guide/
See you tomorrow!
⏰ Final Reminder: iDempiere v13 Testing Starts Tomorrow at 9 AM CET / 8 AM UTC ⏰
Dear community,
The much-anticipated community testing days start tomorrow! Here are all the details to get ready:
Testing hours: 9:00 AM to 7:00 PM Central European Time (8:00 AM to 4:00 PM UTC) on Tuesday and Wednesday. Check your local time here
Collaboration: Join us in the #triage Mattermost channel for live coordination and support
Test cases: Use the test case document. If you need edit access, request it now here
Bug reporting: Follow the process outlined in the kickoff blog post
Before tomorrow morning, please check:
Can you log in successfully into the test servers?
Have you decided which module or feature to test first?
Are you in the #triage channel?
If you experience any issues, ask for help in #triage tonight or early tomorrow morning.
The
test environments have been upgraded to PostgreSQL 18, allowing
everyone to test against this latest version and identify any potential
issues or considerations related to the new PostgreSQL features and
behavior.
All
contributions during these testing days will be counted and
contributors will be publicly credited and recognized for their valuable
work.
Thank you for your dedication. Let’s make v13 the best version yet!
Looking forward to working with all of you.
iDempiere v13 Community Testing - Final Summary & Recognition
Testing days are officially closed, the document is locked, and here are the final numbers:
115 test cases completed in total
36 bugs reported (including important ones to fix before release)
Final Leaderboard:
Tenthplanet – 61 test cases completed / 28 bugs reported
Diego Ruiz – 16 test cases / 2 bugs
Andres Lopez – 11 test cases / 1 bug
Mohamed Dernoun – 9 test cases
Evan Sutherland – 4 test cases
Guilherme Vesco – 3 test cases
Yahya Kammukutty – 3 test cases / 3 bugs
Murilo Habermann – 3 test cases / 1 bug
Alberto Martins – 2 test cases
Carlos Ruiz – 2 test cases / 1 bug
Naslim Madrodji – 1 test case
👏 Big thanks to all testers – whether you ran a single scenario or dozens, every test helped. Extra shout‑out to those who created new test cases and to everyone who kept the #triage channel active, answering questions and coordinating work.
Why this matters
We identified some particularly important bugs that must be fixed before the v13 upgrade.
The breadth of test cases (115!) gives us strong coverage across modules and NF12/NF13 features.
This work directly improves the stability and reliability of the upcoming release for all users.
What happens next
Community will work on fixing the reported bugs, prioritizing the critical ones.
After those fixes land, we'll schedule a follow‑up community testing round focused on verifying the fixes and retesting affected areas.
We'll also use the test cases and feedback to refine documentation and future testing cycles.
Thank you again for making this a truly community‑driven release.