Ledger testing

Related: Command line flags

Performing QA and/or debugging the ledger (Brave Payments) is easy from the command line.

Available options

Option	Example value	Description
LEDGER_VERBOSE	true	Output verbose logs. Critical for debugging
LEDGER_NO_DELAY	true	Call the run method every 5 seconds instead of delaying X minutes (sent back from client)
LEDGER_NO_FUZZING	true	When run processes, don't fuzz. Fuzzing will push back the contribution date if you don't have enough time visited on sites (~30 mins?)
LEDGER_ENVIRONMENT	staging	Used to use a non-production environment. Currently only staging is supported

Running from source

If you're on Windows, you should use Git Bash or set the environment variables (see instructions in packaged build section). Providing the options should be as easy as:

LEDGER_VERBOSE npm run start

Packaged builds

If you're using a packaged build on Windows, you'll want to use mingw (ex: from Git Bash) OR set the options manually as environment variables. Linux and macOS, you can pass them when invoking Brave

Windows using mingw (from Git Bash)

cd ~/AppData/Local/Brave/app-0.19.110/
LEDGER_VERBOSE=true ./Brave

Windows using cmd.exe

Set the environment variables

• Windows key > type environment variables > pick Edit the system environment variables
• Click Environment Variables...
• Under System variables, add new environment variables for the options above
• Open cmd.exe and type the following (change version as needed)

cd %USER_PROFILE%\AppData\Local\Brave\app-0.19.110
Brave.exe

Linux

LEDGER_VERBOSE=true Brave

macOS

LEDGER_VERBOSE=true /Applications/Brave.app/Contents/MacOS/Brave