summaryrefslogtreecommitdiffstats
path: root/QtMobility/sys_versitorganizer/sys_versitorganizer.qtt
blob: dc5424a29672ed37edc7dbcdfed264c1a71457ac (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
/****************************************************************************
**
** Copyright (C) 2010 Nokia Corporation and/or its subsidiary(-ies).
** All rights reserved.
** Contact: Nokia Corporation (qt-info@nokia.com)
**
** This file is part of QtUiTest.
**
** $QT_BEGIN_LICENSE:LGPL$
** No Commercial Usage
** This file contains pre-release code and may not be distributed.
** You may use this file in accordance with the terms and conditions
** contained in the Technology Preview License Agreement accompanying
** this package.
**
** GNU Lesser General Public License Usage
** Alternatively, this file may be used under the terms of the GNU Lesser
** General Public License version 2.1 as published by the Free Software
** Foundation and appearing in the file LICENSE.LGPL included in the
** packaging of this file.  Please review the following information to
** ensure the GNU Lesser General Public License version 2.1 requirements
** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.
**
** In addition, as a special exception, Nokia gives you certain additional
** rights.  These rights are described in the Nokia Qt LGPL Exception
** version 1.1, included in the file LGPL_EXCEPTION.txt in this package.
**
** If you have questions regarding the use of this file, please contact
** Nokia at qt-info@nokia.com.
**
**
**
**
**
**
**
**
** $QT_END_LICENSE$
**
****************************************************************************/

//TESTED_COMPONENT=src/versitorganizer

// Note for test cases relating to  functionality such as add event see test relating to src/organizer
testcase = {

        import_ical: function()
        {
            prompt(twiki('---++ Import iCalendar items

        1. Launch the *calendardemo* application
        1. On app menu, select \'Delete all items\' to insure you are dealing with a pristine calendar
        1. As required transfer exampleEvents.ics onto a location on the target
        1. On app menu, select \'Import items\' menu entry
        1. In file dialog that presents select the exampleEvents.ics that was transfer to the target
        1. Click \'Open\'
        1. In the case of the importing exampleEvents.ics:
            1. Verify there is now the following event:
                | Subject       | \'Bastille Day Party\'        |
                | Start time    | July 14, 1997 17:00 (UTC)     |
                | End time      | July 15, 1997 03:59:59 (UTC)  |
            1. Verify there is the following Todo:
                | Subject   | \'Submit Income Taxes\'   |
                | Time      | April 15, 1998 |
            1. if the platform(backend) supports journal entries:
                | Subject   | \'Project Report\' |
                | Time      | March 24, 1997 |
           * *Hint:* Possibly using the target system\'s Todo, Calendar and Journal applications will be easiest to verify above details
        1. On app menu, select \'Delete all items\'
        1. Close the *calendardemo* application
            '));
        },

        export_ical: function()
        {
             prompt(twiki('---++ Export iCalendar items

        1. Launch the *calendardemo* application
        1. On app menu, select \'Delete all items\' to insure you are dealing with a pristine calendar
        1. Verify that the current backend is the best to suit device
        1. Add *valid* events
            1. Select \'Add Event\' menu entry (maybe listed under \'Options\' menu)
            1. Enter event details:
                | Subject      | \'Event 1\' |
                | Start time   | today\'s date, 08:00 AM |
                | End time     | today\'s date, 01:00 PM |
                | Alarm        | \'30 minutes before\' |
                | Repeat       | \'None\' |
            1. Click \'Save\' button
            1. Select \'Add Event\' menu entry (maybe listed under \'Options\' menu)
            1. Enter event details:
                | Subject      | \'Event 2\' |
                | Start time   | tomorrow\'s date, 02:00 PM |
                | End time     | tomorrow\'s date, 01:00 PM |
                | Alarm        | \'15 minutes before\' |
                | Repeat       | \'None\' |
            1. Click \'Save\' button
        1. Add a *valid* Todos:
            1. Select: \'Add Todo\' menu entry (maybe listed under \'Options\' menu)
            1. Enter Todo detail:
                | Subject       | \'Todo 1\'                    |
                | Start time    | today\'s date 08:00 AM        |
                | End time      | today\'s date 04:00 PM        |
                | Priority      | \'High\'                      |
                | Status        | default                       |
                | Alarm option  | \'30 minutes before\'         |
            1. Click \'Save\' button
            1. Select: \'Add Todo\' menu entry (maybe listed under \'Options\' menu)
            1. Enter Todo detail:
                | Subject       | \'Todo 2\'                    |
                | Start time    | tomorrow\'s date 03:00 PM     |
                | End time      | tomorrow\'s date 04:00 PM     |
                | Priority      | \'Low\'                       |
                | Status        | default                       |
                | Alarm option  | \'5   minutes before\'        |
            1. Click \'Save\' button
        1. If platform(backend) supports Journal entries then add a Journal entry:
            1. Select \'Add Journal\' menu entry (maybe listed under \'Options\' menu)
            1. Enter event details:
                | Subject    | \'Journal 1\' |
                | Time       | today\'s date, 08:00 AM |
                | Alarm      | \'30 minutes before\' |
            1. Click \'Save\' button
        1. If platform(backend) supports Journal entries then add a journal entry for later today:
            1. Select \'Add Journal\' menu entry (maybe listed under \'Options\' menu)
            1. Enter event details:
                | Subject    | \'Journal 2\' |
                | Time       | today\'s date at 02:00 PM |
                | Alarm      | \'15 minutes before\' |
            1. Click \'Save\' button
        1. On app menu, select \'Export items\' menu entry
        1  Enter/select suitable location saving as testcalendar.ics
        1. Click on \'Save\'
        1. Ideally the testcalendar.ics be opened on a separate system and its contents validated, if that is not possible then ..
            1. On app menu, select \'Delete all items\' to remove all calendar items
            1. Close the *calendardemo* application
            1. Launch the *calendardemo* application
            1. On app menu, select menu entry \'Import items\'
            1. Select location for testcalendar.ics entered earlier
            1. Click \'Select\' button
            1. Verify that calendar items \'Event 1\', \'Event 2\', \'Todo 1\' and \'Todo 2\' are present and have expected details
            1. If platform(backend) supports Journal entries then Verify that calendar items \'Journal 1\' and \'Journal 2\' are present and have expected details
        1. Delete events \'Event 1\', \'Event 2\', \'Todo 1\', \'Todo 2\', \'Journal 1\' and \'Journal 2\' (using native calendar application if neccessary)
        1. Close the *calendardemo* application
             '));
        },
}