i.e. implement the same auto-complete functionality as the Action field when "{" is entered, but referencing the config variables.
There may be two or more config files with variables set up in each that don't 100% match the other configurations. For example, Config 1 has variables A, B and C. Config 2 has variables B, C and D. I think in this case we just build the auto-completion functionality around the superset of these - (A, B, C, D). If the user selects Config 1 at run-time and uses variable D then the test will fail, but that's what you'd expect to happen.
Add auto-complete for environment variables.
i.e. implement the same auto-complete functionality as the Action field when "{" is entered, but referencing the config variables.
There may be two or more config files with variables set up in each that don't 100% match the other configurations. For example, Config 1 has variables A, B and C. Config 2 has variables B, C and D. I think in this case we just build the auto-completion functionality around the superset of these - (A, B, C, D). If the user selects Config 1 at run-time and uses variable D then the test will fail, but that's what you'd expect to happen.