#276: Support for independent test development
-------------------------+--------------------------------------------------
Reporter: jlaska | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: 0.5.0
Component: core | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Comment (by tflink):
Replying to [comment:3 jskladan]:
> I'd say that the developers should be able to use whatever programming
language they want. With interprets, this is no big deal, using the
runtest.{whatever} syntax. For C programs (and such), the developer can
use e.g. runtest.sh, which will do the setup (as installing gcc, compiling
the code of the actual test, and launching it.
Personally, I would lean more towards putting test dependencies into the
wrapper. That way we have more easily available metadata for test
requirements and might be more able to get around the requirement for root
access in all cases.
> The wrapper would then auto-find and launch such runtest.xyz. As a
parameter, it might pass a path to temp file, in which the test would
store the results let's say in a json dictionary filled with values to the
standardized keys(i.e. result, summary, highlights, ...) and possibility
of adding some custom ones.
+50. I like this idea. JSON is nice and well-defined in addition to being
well-supported in any number of languages (less work for us and test
maintainers). It's also really flexible if we wanted to go towards things
like couchdb or a RESTful interface in the future.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/276#comment:6>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
_______________________________________________
autoqa-devel mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/autoqa-devel
