Quote:
Originally Posted by Indalecio
I think you're pointing to something right: it has definitely something to do with the way people use shell scripts.
Apart from performing quickly one-time tasks as you supposed in your reply, I heavily use shell scripts to maintain a system interface as well as a bunch of utilities securing the data input/output from the system I'm responsible for.
Yes, I also use scripting in some more complex tasks and, of course, I try to assure a minimum quality in terms, mainly, of documentation, comments, version control, etc. But in this world of sysadmins, this task is up to you. In some way it's a matter of making your life easy. Specially when you mantain a great amount of machines and you work in a huge team. But again, no matter how complicated your scripts are, they're not considered as apps. However, that does not mean that those QA techniques or procedures are not suitable for scripting "apps". Even more, in some cases it could be useful.
Quote:
Now, not many people will actually look deeper into these interface scripts apart from me and a few team members. However, I just wonder if this would justify the fact we have no quality assurance on these scripts, as they almost are as important as the code used behind the interface.
That's what I say above: QA It's up to you.
Quote:
I think I will implement some kind of a basic qa-script to secure at least documentation, backup and version control. The rest is more or less pointless as long as the code's visibility and a few more things like the usage specification and the code comments look fine.
Very interesting. I've never thought of implementing that... I just practice my own "QA" just to help myself (and partners) beacuse, nobody's gonna check my scripts. Perhaps, only, their functionality but that's all.
Regards.