Merge lp:~pkunal-parmar/ubuntu-calendar-app/TapToCreateEvent into lp:ubuntu-calendar-app
| Status: | Merged | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Approved by: | Alan Pope πΊπ§π± π¦ on 2015-05-18 | ||||||||
| Approved revision: | 631 | ||||||||
| Merged at revision: | 646 | ||||||||
| Proposed branch: | lp:~pkunal-parmar/ubuntu-calendar-app/TapToCreateEvent | ||||||||
| Merge into: | lp:ubuntu-calendar-app | ||||||||
| Diff against target: |
164 lines (+47/-12) 6 files modified
NewEvent.qml (+6/-0) TimeLineBase.qml (+15/-2) TimeLineBaseComponent.qml (+7/-1) WeekView.qml (+0/-7) tests/autopilot/calendar_app/tests/test_monthview.py (+5/-0) tests/autopilot/calendar_app/tests/test_weekview.py (+14/-2) |
||||||||
| To merge this branch: | bzr merge lp:~pkunal-parmar/ubuntu-calendar-app/TapToCreateEvent | ||||||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Ubuntu Phone Apps Jenkins Bot | continuous-integration | Approve on 2015-05-09 | |
| Nicholas Skaggs | Needs Fixing on 2015-04-23 | ||
| Alan Pope πΊπ§π± π¦ | 2015-03-25 | Needs Fixing on 2015-04-13 | |
|
Review via email:
|
|||
Commit Message
Resolves Bug #1378380
Add event on tap
Description of the Change
Resolves Bug #1378380
Add event on tap
| Alan Pope πΊπ§π± π¦ (popey) wrote : | # |
Tapping created an event at 21:26, I think it should create an event which locks to the nearest 30 minutes.
The event is created, and then two more button presses are required (tap event, tap edit) to edit the event to change the title from "Untitled". Would it make more sense to go directly to edit event when created?
| Kunal Parmar (pkunal-parmar) wrote : | # |
> Tapping created an event at 21:26, I think it should create an event which
> locks to the nearest 30 minutes.
>
As per current implementation we are truncating minutes and creating event for currently touched hour.
It should have created event rounding to hour, for your case it should have created event on 21:00 to 22:00
Can you confirm once more ?
> The event is created, and then two more button presses are required (tap
> event, tap edit) to edit the event to change the title from "Untitled". Would
> it make more sense to go directly to edit event when created?
This can be done
FAILED: Continuous integration, rev:617
http://
Executed test runs:
UNSTABLE: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
FAILED: Continuous integration, rev:618
http://
Executed test runs:
UNSTABLE: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Kunal Parmar (pkunal-parmar) wrote : | # |
so issue with jenkins was, first day was not visible but AP was trying to click on first day, which it could not see and thus AP fails.
Now scrolling view to make first day visible.
FAILED: Continuous integration, rev:619
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
PASSED: Continuous integration, rev:621
http://
Executed test runs:
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
FAILED: Autolanding.
More details in the following jenkins job:
http://
Executed test runs:
UNSTABLE: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
| Alan Pope πΊπ§π± π¦ (popey) wrote : | # |
testtools.
reference = datetime.
actual = datetime.
So we create an event on the half hour but the test always assumes it's on the hour, so that needs fixing.
| Kunal Parmar (pkunal-parmar) wrote : | # |
Sure, I'll fix this and other ap fail with week number Mr.
FAILED: Continuous integration, rev:622
http://
Executed test runs:
UNSTABLE: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Kunal Parmar (pkunal-parmar) wrote : | # |
From Video, test case seems to be running fine. There seems some issue with Jenkins server. Seems like python is getting some wrong date.
like in below log,
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
Eventually(
File "/usr/lib/
raise mismatch_error
testtools.
as you can see from failure, fail happens on 16th April, so today is 16, but python is expecting 1.
Which is wrong.
FAILED: Continuous integration, rev:624
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
PASSED: Continuous integration, rev:625
http://
Executed test runs:
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Kunal Parmar (pkunal-parmar) wrote : | # |
It was once approved by Alan so approving it again
FAILED: Autolanding.
More details in the following jenkins job:
http://
Executed test runs:
UNSTABLE: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
| Nicholas Skaggs (nskaggs) wrote : | # |
Kunal, ideally we should have a test that covers tapping to create an event. Since event creation is well covered, this test could be written easily enough by opening the dayview and tapping under a few scenarios (on an event, on a blank timeslot, between slots), ensuring the proper response for each.
- 626. By Kunal Parmar on 2015-04-29
-
logging
FAILED: Continuous integration, rev:626
http://
Executed test runs:
UNSTABLE: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 627. By Kunal Parmar on 2015-05-07
-
typo resolved
FAILED: Continuous integration, rev:627
http://
Executed test runs:
UNSTABLE: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 628. By Kunal Parmar on 2015-05-07
-
AP fix
FAILED: Continuous integration, rev:628
http://
Executed test runs:
UNSTABLE: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 629. By Kunal Parmar on 2015-05-07
-
ap fix
FAILED: Continuous integration, rev:629
http://
Executed test runs:
UNSTABLE: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 630. By Kunal Parmar on 2015-05-07
-
AP fix by selecting today
- 631. By Kunal Parmar on 2015-05-09
-
pep8
FAILED: Continuous integration, rev:630
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
PASSED: Continuous integration, rev:631
http://
Executed test runs:
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://


FAILED: Continuous integration, rev:616 91.189. 93.70:8080/ job/ubuntu- calendar- app-ci/ 1111/ 91.189. 93.70:8080/ job/generic- mediumtests- utopic/ 2427 91.189. 93.70:8080/ job/generic- mediumtests- utopic/ 2427/artifact/ work/output/ *zip*/output. zip 91.189. 93.70:8080/ job/ubuntu- calendar- app-utopic- amd64-ci/ 582 91.189. 93.70:8080/ job/ubuntu- calendar- app-vivid- amd64-ci/ 108
http://
Executed test runs:
UNSTABLE: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild: 91.189. 93.70:8080/ job/ubuntu- calendar- app-ci/ 1111/rebuild
http://