Interesting topic with a different perspective.
Here is what my little experience with this tab; rearely have to go that tab and look at the properties.
I would think, that is designed and kept there like that after a thought process only.
Here are the use cases for the same and I practice:
1. Usually I do not have to set them manually / edit the values any time.
2. These properties are set automatically by:
a. Groovy Script Test step
b. Script Assertions
c. Setup / Tear Down scripts
3. Rarely use them manually if there are any static values either for case / suite / project level and still being flexible and not hard-coded values.
4. At times, also use property file and load all of them in one go.
So, basic idea, I assume, is for automation & no hard-coded scripts, flexibility.
Would love to hear your use cases.
