I'm thinking about a project for myself and I'm curious about some things:
Is there a tool available to automate (relval report-results)? Something
like a template with check boxes and text fields you could fill in as
you test and then do something like (relval post) and Yeah! all the
results would get posted.
Is there a text file posted somewhere that contains all the command line
commands that get used in the course of release testing? Such might be
handy for those who might like to automate some or all of their testing.
Just trading searches and typing for grab one file then cut and paste.
I want to experiment with automating most of my release testing. Then I
could test more often and not contend with my typos and such.
My idea is to connect 2 PCs together via USB. One PC would be running
Python pretending to be the keyboard on the test machine. So of course I
need a Python library that provides for keyboard emulation. I would
setup the commands so stdout and stderr go to files I could use to parse
results to a relval template. I understand that posting back to relval
presents more problems than just having a template. To bypass all of
that I have considered that I could restrict all such testing to
Rawhide. and just send a template of results to @test at the end. Though
I might need to do something other than that as I doubt everyone would
enjoy getting my frequent Rawhide test reports.
I understand that some tests require ears and eyes; so results can't be
parsed from a file. Yes, it's sort of just duplicating what coconut
does, but at least it would be done on a different bare metal machine.
Also, I doubt that coconut does it this way; so it would be a bit of a
different environment.
I suspect I'm lining up a lot of hours for myself. I doubt that the
Python library I need exists; so my first task would be to write the
library. The elapsed time is probably measured in years, but I have and
have had long term projects. The possibility that this would be a
foolish waste of time has occurred to me.
Another question is would any of this be useful to the Fedora Project?
A million ideas a day a hundred good ones :-)
All advice, opinions, criticisms, etc. are welcome.
Have a Great Day!
Pat (tablepc)
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
