Ticket #60 (closed proposed-project: wontfix)

Opened 7 years ago

Last modified 2 years ago

Unit testing of GUI code (and whole programs)

Reported by: mahogny@… Owned by: none
Priority: OK Keywords:
Cc: Topic: Tools
Difficulty: unknown Mentor: not-accepted

Description (last modified by shelarcy) (diff)

testing GUIs automatically is currently very messy. write a tool for the job! I would expect that you pick a haskell GUI of your choice and then write a middle-layer between the GUI and the program (or dig into the library internals how to extract the GUI structure). you might then feed this in a good format to QuickCheck? or just add a user-clicks-like-crazy-crash-test.

Interested Mentors

  • Kido Takahiro (shelarcy) <shelarcy@…>

Interested Students

Change History

Changed 7 years ago by mahogny

Interested mentors:

* Johan Henriksson (mahogny@…)

Interested students:

Changed 7 years ago by mahogny

  • description modified (diff)

Changed 7 years ago by andrea

  • description modified (diff)

Changed 6 years ago by mahogny

  • description modified (diff)

Changed 5 years ago by shelarcy

  • priority set to not yet rated
  • description modified (diff)

Changed 5 years ago by nominolo

  • priority changed from not yet rated to OK

Changed 2 years ago by tibbe

  • status changed from new to closed
  • resolution set to wontfix

Too hard for a student. There are already some open source libraries out there (e.g. Selenium) for some use cases. We also don't have a lot of Haskell UI apps worth testing (i.e. we better focus on UI libraries before testing UI code).

Note: See TracTickets for help on using tickets.