I think you'll need to deal with the NUL-separated strings, and restart the shell to see the result you're looking for:
$ $$
bash: 9166: command not found
$ export TESTVAR=test_question
# at this point, you can check `/proc/9166/environ`, but `TESTVAR` won't show up until the shell is re-started
$ tr '\0' '\
' < /proc/9166/environ
SHELL=/bin/bash
NO_AT_BRIDGE=1
PWD=/home/pi
LOGNAME=pi
# ... etc, etc - the env var TESTVAR is not there...
$ tr '\0' '\
' < /proc/9166/environ | grep TESTVAR
$
# re-start bash & try again:
$ exec bash
$ tr '\0' '\
' < /proc/9166/environ | grep TESTVAR
TESTVAR=test_question
$
Attribution to @aviro & @stephenkitt for the simplifications (see comments)