forked from php/web-qa
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathprojects.php
More file actions
117 lines (114 loc) · 4.57 KB
/
projects.php
File metadata and controls
117 lines (114 loc) · 4.57 KB
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
<?php
include("include/functions.php");
$TITLE = "Projects & Goals [PHP-QAT: Quality Assurance Team]";
$SITE_UPDATE = date("D M d H:i:s Y T", filectime(__FILE__));
/* $Id$ */
common_header();
?>
<table width="70%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td>
<td width="100%">
<h1>PHP-QAT Goals</h1>
</td>
<td width="10"><img src="gfx/spacer.gif" width="10" height="1"></td>
</tr>
<tr>
<td width="10"> </td>
<td width="100%">
<h3>Release Candidates Testing and QA</h3>
</td>
<td width="10"> </td>
</tr>
<tr>
<td width="10"> </td>
<td width="100%">
<ul>
<li><span class="lihack">Release Candidate Build </span></li>
<li><span class="lihack">Automated Smoke Tests </span></li>
<li><span class="lihack">Automated QA Checklists </span></li>
<li><span class="lihack">Automated Regression Tests </span></li>
</ul>
</td>
<td width="10"> </td>
</tr>
<tr>
<td width="10"> </td>
<td width="100%">
<h3>Modify The Bug Database Interface</h3>
</td>
<td width="10"> </td>
</tr>
<tr>
<td width="10"> </td>
<td width="100%">
<h4>The interface should:<br>
</h4>
</td>
<td width="10"> </td>
</tr>
<tr>
<td width="10"> </td>
<td width="100%">
<ul>
<li><span class="lihack">reduce the occurance of multiple reports on the same bug</span></li>
<li><span class="lihack">improve the accuracy of the reports </span></li>
<li><span class="lihack">make it easier for the QAT to reproduce the bug </span></li>
<li><span class="lihack">track the solution to the bug </span></li>
</ul>
</td>
<td width="10"> </td>
</tr>
<tr>
<td width="10"> </td>
<td width="100%">
<h3>Bug Hunting</h3>
</td>
<td width="10"> </td>
</tr>
<tr>
<td width="10"> </td>
<td width="100%">
<ul>
<li><span class="lihack"><a href="handling-bugs.php">analysing/closing existing bug reports</a> at bugs.php.net </span></li>
<li><span class="lihack">analysing new bugs posted on the php-dev list </span></li>
<li><span class="lihack">actively seeking and tracking bugs on available platforms </span></li>
<li><span class="lihack">monitoring/reviewing information from existing PHP mailing lists</span></li>
</ul>
</td>
<td width="10"> </td>
</tr>
<tr>
<td width="10"> </td>
<td width="100%">
<h3>Provide Client-Side Bug Reporting via PHP Interpreter</h3>
</td>
<td width="10"> </td>
</tr>
<tr>
<td width="10"> </td>
<td width="100%">
<ul>
<li><span class="lihack">Add functionality to PHP to help php users submit accurate bugs.
</span></li>
<li><span class="lihack">Probably the best solution that has been proposed is the addition
of a submit_bug() function that would automatically send platform
data, along with PHP interpreter state when it is called. This
solution would address the security concerns that have been raised
by the possible display of platform information to malicious visitors.
</span></li>
<li><span class="lihack">Bugs gathered from this source would need to be filtered by
an agent before they could be considered truly useful. </span></li>
<li><span class="lihack">Note that filtering many spurious bug reports should be relatively
simple. Bug reports that were generated due to parse errors could
be ignored or flagged as low priority. </span></li>
<li><span class="lihack">However, all of this would require developer involvement and
is probably the least plausible goal! </span></li>
</ul>
</td>
<td width="10"> </td>
</tr>
</table>
<?php
common_footer();
?>