Gedit Test Needed: Test Highlighted Text
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Autopilot Tests |
Fix Released
|
Undecided
|
Dan Chapman |
Bug Description
Currently, there isn't actually a way this test could fail. And doesn't introspect any of the objects properties that it is testing.
With it just using the keyboard throughout this test. There is no way of reliably determining the actions it is supposed to implement actually occurred.
To further improve this test it needs
1) Introspect the search box, check its visible
2) Enter search query and assert that the search box text property matches our query
3) Now, although we can see the documents text through its buffer property we cannot see it has been highlighted, so instead when doing a search say for 'The' if you then hit enter twice 'The' will get deleted and we can check the buffer property that it has in fact gone. So this way we can say well gedit 'picked up' (highlighted) our search, which we were then able to remove.
Related branches
- Nicholas Skaggs (community): Approve
-
Diff: 1347 lines (+936/-357)9 files modifiedubuntu_autopilot_tests/gedit/__init__.py (+154/-0)
ubuntu_autopilot_tests/gedit/samples/gedit.c (+8/-0)
ubuntu_autopilot_tests/gedit/samples/gedit.cpp (+8/-0)
ubuntu_autopilot_tests/gedit/samples/gedit.py (+6/-0)
ubuntu_autopilot_tests/gedit/samples/gedit.vala (+9/-0)
ubuntu_autopilot_tests/gedit/samples/gedit.xml (+21/-0)
ubuntu_autopilot_tests/gedit/samples/gedit1.c (+8/-0)
ubuntu_autopilot_tests/gedit/samples/test (+1/-0)
ubuntu_autopilot_tests/gedit/test_gedit.py (+721/-357)
description: | updated |
tags: | added: todo |
Changed in ubuntu-autopilot-tests: | |
assignee: | nobody → Dan Chapman (dpniel) |
status: | New → In Progress |
Changed in ubuntu-autopilot-tests: | |
status: | In Progress → Fix Committed |
Changed in ubuntu-autopilot-tests: | |
status: | Fix Committed → Fix Released |