Hi Petri! When the integration tests start cargo for Fineract, they provide a > specific set of configurations for Tomcat that configure Fineract into the > correct security mode for testing - see e.g the cargo config block in > fineract/oauth2-tests/build.gradle. Did you start your standalone server > with the same configs? >
Yes, well, I tried to. It seems like there's still some runtime difference I was unable to account for. See the growing list of environment variables I shared earlier in this thread (inline <https://lists.apache.org/thread/343f01c4c0o1dfz45z219gn8cfxfqord> and attached <https://lists.apache.org/thread/2vrb64lhgscc4n3yw97o55ttqxz2lodj> as env.sh <https://lists.apache.org/api/email.lua?attachment=true&id=2vrb64lhgscc4n3yw97o55ttqxz2lodj&file=a510c3d82cc0629a5968dd05a49453272b71af812b1fa0137418402989904981> ). I don't think there's much of a gap if someone wants to remove cargo entirely, just need to resolve the activemq/spring jms conflict to fix the 16 failing tests. Probably. I'm not familiar with the issues you brought up around security tests needing cargo. I talked with Aleks about replacing the integration test cargo bits with, e.g. a local Fineract instance running in Docker. Seems like that's a good way to go. Related / asides: The current best source of how to test Fineract from the command line is the files in .github/workflows/ . It's too bad these *only* work on GitHub as written. I'll propose some updates to "INSTRUCTIONS: How to execute Integration Tests" in the top-level README.md file since what's there now is incorrect. Assuming those .github/workflows/ files are the most current and useful working description of a full build & test run, it's stunning to me that it could take an individual a full workday to reproduce that at home! For testing from IntelliJ, https://fineract-academy.com is the most current and useful. Best and thanks, -Adam
