Warning, /plasma/drkonqi/Testing.md is written in an unsupported language. File is not indexed.

0001 <!--
0002     SPDX-License-Identifier: CC0-1.0
0003     SPDX-FileCopyrightText: 2019-2021 Harald Sitter <sitter@kde.org>
0004 -->
0005 
0006 # Exec
0007 
0008 Drkonqi also doesn't technically require a process to actually crash, you can
0009 simply run it manually on any old pid. Do note that in most cases you only need
0010 to define the pid, however not giving certain cmdline options can change
0011 behavior somewhat drastically (e.g. kdeinit vs. notkdeinit behaves radically
0012 different as far as process name detection goes)
0013 
0014 example command to doctor a running dolphin:
0015 
0016 ```
0017 DRKONQI_HTTP_DELAY_MS=1000 \
0018 DRKONQI_TEST_MODE=1 \
0019 DRKONQI_IGNORE_QUALITY=1 \
0020 DRKONQI_KDE_BUGZILLA_URL="https://bugstest.kde.org/" \
0021 bin/drkonqi \
0022 -platform xcb -display :0 --appname org_kde_powerdevil --apppath /usr/lib/x86_64-linux-gnu/libexec --signal 11 --pid `pidof dolphin` --startupid 0 --restarted --bugaddress submit@bugs.kde.org --dialog
0023 ```
0024 
0025 # Environment
0026 
0027 The following environment variables may be used to test drkonqi with actual reports.
0028 
0029 - DRKONQI_TEST_MODE: influences everything and the kitchen sink, influences
0030   UI behavior to streamline test-reporting and also forces bugstest.kde.org
0031   use so test reports do not clutter up the live bugzilla
0032 - DRKONQI_IGNORE_QUALITY: ignores quality constraints (e.g. backtrace scores
0033   are always assumed perfect)
0034 - DRKONQI_KDE_BUGZILLA_URL: changes the kde bugzilla url (only really useful
0035   to set this to bugstest.kde.org - must end with slash)
0036 - DRKONQI_HTTP_DELAY_MS: introduce a delay on every single API request
0037   (simulates slow connection)
0038 - DRKONQI_SKIP_DUPES: skip duplicate checking (is faster and allows filing dupes)
0039 
0040 # Backends
0041 
0042 Drkonqi has a number of backends that may be used. Backends are stacked by
0043 order of preference, backends in the directory of the binary are most preferred.
0044 This means that you can dump debuggers/internal/ into your build's bin/
0045 directory and override for example gdb. This essentially allows you to replace
0046 the gdb debugger with a `cat` of a fixture file to not have to trace live
0047 processes at all.