summaryrefslogtreecommitdiff
path: root/Testing_Reference/fr-FR/Introduction.po
blob: 600e5827c301a1458932e37445818fcbbd9b13c2 (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
# 
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2012-08-13T14:49:27\n"
"PO-Revision-Date: 2012-08-13T14:49:27\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Tag: title
#, no-c-format
msgid "Introduction"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Bugzilla's Testopia extension, along with the Kolab Python utility suite, is leading in the way Kolab executes its testing. Note that there are many components that require testing, and many deployment scenarios (<emphasis>environments</emphasis>) need to be replicated for accurate representation of test results."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Collecting those test results, and reporting based on these results, is performed through Bugzilla's Testopia extension. Reporting is important, because the premature identification of potentially problematic areas or sour spots enables us to shift attention and resources to that area and give it the appropriate amount of attention before any such problems hit any of our consumers."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Bugzilla's Testopia"
msgstr ""

#. Tag: para
#, no-c-format
msgid "In Testopia, a <emphasis>test plan</emphasis> attached to a Bugzilla product. Each test plan contains a number of <emphasis>test cases</emphasis>, each case representing a single action to be taken of which the results can be measured."
msgstr ""

#. Tag: para
#, no-c-format
msgid "These plans enable concise testing of a single product component, such as the <application>Kontact</application>, but of course the outcome of the tests is not dependent solely on that single product component &ndash;Kolab is a complete environment of interconnected, smaller components. As such, the test cases in each plan are ran against a <emphasis>build</emphasis> of the software being tested, said software being deployed into an <emphasis>environment</emphasis>."
msgstr ""

#. Tag: para
#, no-c-format
msgid "These builds and environments, as well as the runs of test cases against said builds and environments can be organized and tracked in Testopia."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Bugs may be created from failed tests, and test cases may be created from bugs."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Actually executing each test case for each build against different environments, however, is a different story; Manually preparing the environment for a test and manually executing the test cases is inefficient, boring, prone to error and not reproducible &ndash;thus painstaking, expensive and not even proper testing."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Kolab's PyKolab"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Amongst other things, we try to automate as much testing as possible with the Kolab Python utilities. Test plans are attached to what we call a <emphasis>suite</emphasis> &ndash;a single suite can contain multiple relevant products&ndash;, each suite containing a number of sets (plans) of tests (cases)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The suites are suites and not products, because a single suite may contain tests targetted at more then one product component. Noted though, most suites indeed target only one product."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Each \"plan\", or series of tests, sort of corresponds with an iteration of a reset of the environment. Suppose user/a@b.com wants an extra folder, of course we don't need to reset the complete environment. However, should user a@b.com no longer exist. Additionally, \"plans\" form a means of categorization."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Each \"case\", or test, represents a single step on our way to completing the report on a Testopia test case, or a fully automated series of steps completing a Testopia test case. The latter obviously assumes the former has been performed before or is trusted to work."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Obtaining the Source Code for PyKolab"
msgstr ""

#. Tag: para
#, no-c-format
msgid "To obtain a copy of PyKolab's source code, please execute the following:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "$ <userinput>git clone git://git.kolab.org/git/pykolab</userinput>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Software Requirements"
msgstr ""

#. Tag: para
#, no-c-format
msgid "You will need <application>autoconf</application> and <application>automake</application> installed in order to run PyKolab directly from source. No installation packages have been provided yet."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Now, navigate into the source code repository root directory, and execute the following commands:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "$ <userinput>autoreconf -v &amp;&amp;./configure</userinput>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Configuration"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Configuration is performed through files similar to <filename>conf/kolab.conf</filename>, all in .ini format. We recommend you look at <ulink url=\"http://git.kolab.org/pykolab/tree/conf/kolab-test-example.conf\"><filename>conf/kolab-test-example.conf</filename></ulink>, copy it, modify it and knock yourself out against your own test environment."
msgstr ""