You could provide Automateaching as a set of modules the user must install locally and then run simple commands like submit --file mysolution.pl, markme, get-more-assignments, pay-course-fees to progress and finally graduate. (example: NYTProf requires to have a module installed and run a few command line utilities to get job done. Or git with all its cli git functionality - especially if you envision a web interface requiring central db, credentials, competitions). The assignments can still be self-contained, independent files, but you will make sure the user has all the Test and other frameworks installed as well.

Once you do that, of course you can package this functionality into a plugin to an existing integrated development environment (IDE). You can see how an IDE offers git functionality for example and more or less follow that.

I always liked building a large system using small utilities specialising in something small. Just like Unix. Then you can glue things together using scripts or the IDE plugin.

So, if I may, one could start with 1) a Makefile to check on required modules, 2) an assignment/lesson file format (which can also include multimedia, slides, code), 3) a small perl script to request a first assignment, have it downloaded (with credentials perhaps), 4) a small perl script to mark a solution, 5) a way to present the lesson and its multimedia - a web browser perhaps?.

Providing an exam-like environment so schools can use to have IT exams would also be a great selling (I mean "selling") point.

bw, bliako