Comment 6 for bug 1367871

@zsombi I must disagree that supporting CLI arguments is a must, in any situation. As we push further to convergence, this may become more evident, but arguments and environment variables are not "the right way" to solve these problems. They are simply the easy way, because we are used to using them, and working in an unsecured environment.

Even for the "actions" support in Unity and that we've ascribed to the .desktop file infrastructure, I'd argue strongly that different command line arguments is the wrong way to do it. Standardized IPC methods would be the best way, similar to how such actions worked on Windows with COM, and developers can easily declare what standard methods it supports, and provide additional methods when needed. These could perhaps encoded in some way in the .desktop file, or some similar manifest file, and the Actions menu built from that and/or live interaction with the app when running.

For testing, and security, the best solution is isolation. Running the app in an environment isolated from the host system, where the test framework controls the environment and the tests poke the app via IPC, a11y, and similar system layers, I think would be the optimal solution.