Test Parser generates warning for properly formatted field declaration lists

[BZngr]

Version 2.5.0.28404
OS: Microsoft Windows NT 10.0.18362.0, x64
Host Product: Microsoft Office x86
Host Version: 16.0.12430.20184
Host Executable: EXCEL.EXE

Observed during NUnit test runs.

Steps to reproduce the behavior:

1. Create a Unit Test in VS
2. Include something like Private mFoo As Long, mFoo1 As Long, mFoo3 As Long in your VBA test code.
3. Run the test
4. In VS Tests Output window you will see lines like:

line 4:21 extraneous input ',' expecting {, ':', REM, NEWLINE, ''', WS, LINE_CONTINUATION}

Changing a test's declaration list to a one-line-per-declaration format does not result in these warning messages. I'm guessing the parser is taking exception to the commas between field declarations. Test still run OK - Creating this issue just in case the warning points to a more important issue.

[Vogel612]

This is strictly speaking not a bug. There might be some parser setup to change in the corresponding unit-test to avoid this warning. In and of itself, this is not impacting the "live" code meaningfully.