[xwiki-devs] [Proposal][QA] Put Test Report Application on xwiki.org
Hello everybody, After several months of fragmented work, I have finally managed to complete the next iteration of Test Report Application [1]. Final parts of the code will be committed next week. Taking into consideration the feedback I received, I implemented several changes into the application to make it more user friendly and robust. In order to put the application in production, Manuel and me converted the Manual Test Report Template [2] into Test Cases to be used by the Test Report Application. These test cases are committed on Github [3]. Now we have 404 Test Cases, grouped in 22 Spaces as follows: 1) Action Menus Tests 2) App Within Minutes Tests 3) Dashboard Macro Tests 4) Page Tabs Tests 5) Rights Tests 6) Tags Tests 7) Wiki Editor Tests 8) WYSIWYG Editor Tests 9) Activity Stream Tests 10) Blog Tests 11) Document Index Tests 12) Panels Tests 13) Search Tests 14) User Profile Tests 15) Wiki Manager Tests 16) Administration Tests 17) Color Themes Tests 18) Jump To Page Tests 19) Register and Authentication Tests 20) Space Macro Tests 21) User Status Tests 22) Workspaces Tests My proposal is that we create a dedicated subwiki for this, qa.xwiki.orgwhere we will deploy the application + test cases. The rationale behind having a dedicated subwiki for this is that we don't want to crowd an already existing subwiki with the test cases and also the spaces which will hold the test execution pages. WDYT ? I am waiting for your opinions/concerns/questions about this. Regards, Sorin B. [1] https://github.com/xwiki-contrib/application-testreporting [2] http://www.xwiki.org/xwiki/bin/view/TestReports/ManualTestReportTemplate [3] https://github.com/xwiki-contrib/application-testreporting-cases
Hi Sorin, On May 31, 2013, at 3:16 PM, Sorin Burjan <[email protected]> wrote:
Hello everybody,
After several months of fragmented work, I have finally managed to complete the next iteration of Test Report Application [1]. Final parts of the code will be committed next week. Taking into consideration the feedback I received, I implemented several changes into the application to make it more user friendly and robust.
In order to put the application in production, Manuel and me converted the Manual Test Report Template [2] into Test Cases to be used by the Test Report Application. These test cases are committed on Github [3]. Now we have 404 Test Cases, grouped in 22 Spaces as follows: 1) Action Menus Tests 2) App Within Minutes Tests 3) Dashboard Macro Tests 4) Page Tabs Tests 5) Rights Tests 6) Tags Tests 7) Wiki Editor Tests 8) WYSIWYG Editor Tests 9) Activity Stream Tests 10) Blog Tests 11) Document Index Tests 12) Panels Tests 13) Search Tests 14) User Profile Tests 15) Wiki Manager Tests 16) Administration Tests 17) Color Themes Tests 18) Jump To Page Tests 19) Register and Authentication Tests 20) Space Macro Tests 21) User Status Tests 22) Workspaces Tests
It would be nice to have a one to one mapping between these categories to maven modules. That will make it much easier to maintain.
My proposal is that we create a dedicated subwiki for this, qa.xwiki.orgwhere we will deploy the application + test cases. The rationale behind having a dedicated subwiki for this is that we don't want to crowd an already existing subwiki with the test cases and also the spaces which will hold the test execution pages.
WDYT ? I am waiting for your opinions/concerns/questions about this.
ok for a dedicated wiki but I'm concerned about its name. If we name it "qa" it means it's going to be used for all QA, i.e. we'll need to move QA pages from dev.xwiki.org to it. I'm not sure we want this from what you describe. So a name like "test.xwiki.org" seems a better name to me. Thanks -Vincent
Regards, Sorin B.
[1] https://github.com/xwiki-contrib/application-testreporting [2] http://www.xwiki.org/xwiki/bin/view/TestReports/ManualTestReportTemplate [3] https://github.com/xwiki-contrib/application-testreporting-cases
Hi Vincent, Naming it "test.xwiki.org" might allow it to be mistaken for something temporary or useless in the future, so something like "testing" would be a better match imho. WDYT? Thanks! On Fri, May 31, 2013 at 4:53 PM, Vincent Massol <[email protected]> wrote:
Hi Sorin,
On May 31, 2013, at 3:16 PM, Sorin Burjan <[email protected]> wrote:
Hello everybody,
After several months of fragmented work, I have finally managed to complete the next iteration of Test Report Application [1]. Final parts of the code will be committed next week. Taking into consideration the feedback I received, I implemented several changes into the application to make it more user friendly and robust.
In order to put the application in production, Manuel and me converted the Manual Test Report Template [2] into Test Cases to be used by the Test Report Application. These test cases are committed on Github [3]. Now we have 404 Test Cases, grouped in 22 Spaces as follows: 1) Action Menus Tests 2) App Within Minutes Tests 3) Dashboard Macro Tests 4) Page Tabs Tests 5) Rights Tests 6) Tags Tests 7) Wiki Editor Tests 8) WYSIWYG Editor Tests 9) Activity Stream Tests 10) Blog Tests 11) Document Index Tests 12) Panels Tests 13) Search Tests 14) User Profile Tests 15) Wiki Manager Tests 16) Administration Tests 17) Color Themes Tests 18) Jump To Page Tests 19) Register and Authentication Tests 20) Space Macro Tests 21) User Status Tests 22) Workspaces Tests
It would be nice to have a one to one mapping between these categories to maven modules. That will make it much easier to maintain.
My proposal is that we create a dedicated subwiki for this, qa.xwiki.orgwhere we will deploy the application + test cases. The rationale behind having a dedicated subwiki for this is that we don't want to crowd an already existing subwiki with the test cases and also the spaces which will hold the test execution pages.
WDYT ? I am waiting for your opinions/concerns/questions about this.
ok for a dedicated wiki but I'm concerned about its name. If we name it "qa" it means it's going to be used for all QA, i.e. we'll need to move QA pages from dev.xwiki.org to it. I'm not sure we want this from what you describe. So a name like "test.xwiki.org" seems a better name to me.
Thanks -Vincent
Regards, Sorin B.
[1] https://github.com/xwiki-contrib/application-testreporting [2] http://www.xwiki.org/xwiki/bin/view/TestReports/ManualTestReportTemplate [3] https://github.com/xwiki-contrib/application-testreporting-cases
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Best Regards, Daniel Patriche XWiki SAS SysAdmin
On May 31, 2013, at 4:38 PM, Daniel Patriche <[email protected]> wrote:
Hi Vincent,
Naming it "test.xwiki.org" might allow it to be mistaken for something temporary or useless in the future, so something like "testing" would be a better match imho. WDYT?
testing, testreports, manualtests, testcentral, testhq, etc. test.xwiki.org is still the best for me by far. The home page will clearly state what it's about so I don't feel it's a problem at all. Especially since it's a wiki for us and not for end users. Thanks -Vincent
Thanks!
On Fri, May 31, 2013 at 4:53 PM, Vincent Massol <[email protected]> wrote:
Hi Sorin,
On May 31, 2013, at 3:16 PM, Sorin Burjan <[email protected]> wrote:
Hello everybody,
After several months of fragmented work, I have finally managed to complete the next iteration of Test Report Application [1]. Final parts of the code will be committed next week. Taking into consideration the feedback I received, I implemented several changes into the application to make it more user friendly and robust.
In order to put the application in production, Manuel and me converted the Manual Test Report Template [2] into Test Cases to be used by the Test Report Application. These test cases are committed on Github [3]. Now we have 404 Test Cases, grouped in 22 Spaces as follows: 1) Action Menus Tests 2) App Within Minutes Tests 3) Dashboard Macro Tests 4) Page Tabs Tests 5) Rights Tests 6) Tags Tests 7) Wiki Editor Tests 8) WYSIWYG Editor Tests 9) Activity Stream Tests 10) Blog Tests 11) Document Index Tests 12) Panels Tests 13) Search Tests 14) User Profile Tests 15) Wiki Manager Tests 16) Administration Tests 17) Color Themes Tests 18) Jump To Page Tests 19) Register and Authentication Tests 20) Space Macro Tests 21) User Status Tests 22) Workspaces Tests
It would be nice to have a one to one mapping between these categories to maven modules. That will make it much easier to maintain.
My proposal is that we create a dedicated subwiki for this, qa.xwiki.orgwhere we will deploy the application + test cases. The rationale behind having a dedicated subwiki for this is that we don't want to crowd an already existing subwiki with the test cases and also the spaces which will hold the test execution pages.
WDYT ? I am waiting for your opinions/concerns/questions about this.
ok for a dedicated wiki but I'm concerned about its name. If we name it "qa" it means it's going to be used for all QA, i.e. we'll need to move QA pages from dev.xwiki.org to it. I'm not sure we want this from what you describe. So a name like "test.xwiki.org" seems a better name to me.
Thanks -Vincent
Regards, Sorin B.
[1] https://github.com/xwiki-contrib/application-testreporting [2] http://www.xwiki.org/xwiki/bin/view/TestReports/ManualTestReportTemplate [3] https://github.com/xwiki-contrib/application-testreporting-cases
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Best Regards,
Daniel Patriche XWiki SAS SysAdmin _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hello Vincent, On Fri, May 31, 2013 at 4:53 PM, Vincent Massol <[email protected]> wrote:
Hi Sorin,
On May 31, 2013, at 3:16 PM, Sorin Burjan <[email protected]> wrote:
Hello everybody,
After several months of fragmented work, I have finally managed to complete the next iteration of Test Report Application [1]. Final parts of the code will be committed next week. Taking into consideration the feedback I received, I implemented several changes into the application to make it more user friendly and robust.
In order to put the application in production, Manuel and me converted the Manual Test Report Template [2] into Test Cases to be used by the Test Report Application. These test cases are committed on Github [3]. Now we have 404 Test Cases, grouped in 22 Spaces as follows: 1) Action Menus Tests 2) App Within Minutes Tests 3) Dashboard Macro Tests 4) Page Tabs Tests 5) Rights Tests 6) Tags Tests 7) Wiki Editor Tests 8) WYSIWYG Editor Tests 9) Activity Stream Tests 10) Blog Tests 11) Document Index Tests 12) Panels Tests 13) Search Tests 14) User Profile Tests 15) Wiki Manager Tests 16) Administration Tests 17) Color Themes Tests 18) Jump To Page Tests 19) Register and Authentication Tests 20) Space Macro Tests 21) User Status Tests 22) Workspaces Tests
It would be nice to have a one to one mapping between these categories to maven modules. That will make it much easier to maintain.
I am not sure I quite understand what you mean with this. You want me to move each space to its own maven module ? I don't understand what are the advantages. Regards, Sorin B.
My proposal is that we create a dedicated subwiki for this, qa.xwiki.orgwhere we will deploy the application + test cases. The rationale behind having a dedicated subwiki for this is that we don't want to crowd an already existing subwiki with the test cases and also the spaces which will hold the test execution pages.
WDYT ? I am waiting for your opinions/concerns/questions about this.
ok for a dedicated wiki but I'm concerned about its name. If we name it "qa" it means it's going to be used for all QA, i.e. we'll need to move QA pages from dev.xwiki.org to it. I'm not sure we want this from what you describe. So a name like "test.xwiki.org" seems a better name to me.
Thanks -Vincent
Regards, Sorin B.
[1] https://github.com/xwiki-contrib/application-testreporting [2] http://www.xwiki.org/xwiki/bin/view/TestReports/ManualTestReportTemplate [3] https://github.com/xwiki-contrib/application-testreporting-cases
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Jun 3, 2013, at 9:56 AM, Sorin Burjan <[email protected]> wrote:
Hello Vincent,
On Fri, May 31, 2013 at 4:53 PM, Vincent Massol <[email protected]> wrote:
Hi Sorin,
On May 31, 2013, at 3:16 PM, Sorin Burjan <[email protected]> wrote:
Hello everybody,
After several months of fragmented work, I have finally managed to complete the next iteration of Test Report Application [1]. Final parts of the code will be committed next week. Taking into consideration the feedback I received, I implemented several changes into the application to make it more user friendly and robust.
In order to put the application in production, Manuel and me converted the Manual Test Report Template [2] into Test Cases to be used by the Test Report Application. These test cases are committed on Github [3]. Now we have 404 Test Cases, grouped in 22 Spaces as follows: 1) Action Menus Tests 2) App Within Minutes Tests 3) Dashboard Macro Tests 4) Page Tabs Tests 5) Rights Tests 6) Tags Tests 7) Wiki Editor Tests 8) WYSIWYG Editor Tests 9) Activity Stream Tests 10) Blog Tests 11) Document Index Tests 12) Panels Tests 13) Search Tests 14) User Profile Tests 15) Wiki Manager Tests 16) Administration Tests 17) Color Themes Tests 18) Jump To Page Tests 19) Register and Authentication Tests 20) Space Macro Tests 21) User Status Tests 22) Workspaces Tests
It would be nice to have a one to one mapping between these categories to maven modules. That will make it much easier to maintain.
I am not sure I quite understand what you mean with this. You want me to move each space to its own maven module ? I don't understand what are the advantages.
No. I'm suggesting to keep the existing taxonomy: https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core Thanks -Vincent
Regards, Sorin B.
My proposal is that we create a dedicated subwiki for this, qa.xwiki.orgwhere we will deploy the application + test cases. The rationale behind having a dedicated subwiki for this is that we don't want to crowd an already existing subwiki with the test cases and also the spaces which will hold the test execution pages.
WDYT ? I am waiting for your opinions/concerns/questions about this.
ok for a dedicated wiki but I'm concerned about its name. If we name it "qa" it means it's going to be used for all QA, i.e. we'll need to move QA pages from dev.xwiki.org to it. I'm not sure we want this from what you describe. So a name like "test.xwiki.org" seems a better name to me.
Thanks -Vincent
Regards, Sorin B.
[1] https://github.com/xwiki-contrib/application-testreporting [2] http://www.xwiki.org/xwiki/bin/view/TestReports/ManualTestReportTemplate [3] https://github.com/xwiki-contrib/application-testreporting-cases
Hello, I am OK with the name "test". I will put a clear description on the homepage so users will not feel confused. Vincent, could you please create the subwiki ? Regards, Sorin B. On Mon, Jun 3, 2013 at 11:08 AM, Vincent Massol <[email protected]> wrote:
On Jun 3, 2013, at 9:56 AM, Sorin Burjan <[email protected]> wrote:
Hello Vincent,
On Fri, May 31, 2013 at 4:53 PM, Vincent Massol <[email protected]> wrote:
Hi Sorin,
On May 31, 2013, at 3:16 PM, Sorin Burjan <[email protected]> wrote:
Hello everybody,
After several months of fragmented work, I have finally managed to complete the next iteration of Test Report Application [1]. Final parts of the code will be committed next week. Taking into consideration the feedback I received, I implemented several changes into the application to make it more user friendly and robust.
In order to put the application in production, Manuel and me converted the Manual Test Report Template [2] into Test Cases to be used by the Test Report Application. These test cases are committed on Github [3]. Now we have 404 Test Cases, grouped in 22 Spaces as follows: 1) Action Menus Tests 2) App Within Minutes Tests 3) Dashboard Macro Tests 4) Page Tabs Tests 5) Rights Tests 6) Tags Tests 7) Wiki Editor Tests 8) WYSIWYG Editor Tests 9) Activity Stream Tests 10) Blog Tests 11) Document Index Tests 12) Panels Tests 13) Search Tests 14) User Profile Tests 15) Wiki Manager Tests 16) Administration Tests 17) Color Themes Tests 18) Jump To Page Tests 19) Register and Authentication Tests 20) Space Macro Tests 21) User Status Tests 22) Workspaces Tests
It would be nice to have a one to one mapping between these categories to maven modules. That will make it much easier to maintain.
I am not sure I quite understand what you mean with this. You want me to move each space to its own maven module ? I don't understand what are the advantages.
No. I'm suggesting to keep the existing taxonomy: https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core
Thanks -Vincent
Regards, Sorin B.
My proposal is that we create a dedicated subwiki for this, qa.xwiki.orgwhere we will deploy the application + test cases. The rationale behind having a dedicated subwiki for this is that we don't want to crowd an already existing subwiki with the test cases and also the spaces which will hold the test execution pages.
WDYT ? I am waiting for your opinions/concerns/questions about this.
ok for a dedicated wiki but I'm concerned about its name. If we name it "qa" it means it's going to be used for all QA, i.e. we'll need to move
QA
pages from dev.xwiki.org to it. I'm not sure we want this from what you describe. So a name like "test.xwiki.org" seems a better name to me.
Thanks -Vincent
Regards, Sorin B.
[1] https://github.com/xwiki-contrib/application-testreporting [2]
http://www.xwiki.org/xwiki/bin/view/TestReports/ManualTestReportTemplate
[3] https://github.com/xwiki-contrib/application-testreporting-cases
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi Sorin, The wiki has been created at http://test.xwiki.org I'll let you add the content. Right now it doesn't have any Color Theme. Would be great if Caty could help on this :) Thanks -Vincent On Jun 11, 2013, at 12:40 PM, Sorin Burjan <[email protected]> wrote:
Hello,
I am OK with the name "test". I will put a clear description on the homepage so users will not feel confused.
Vincent, could you please create the subwiki ?
Regards, Sorin B.
On Mon, Jun 3, 2013 at 11:08 AM, Vincent Massol <[email protected]> wrote:
On Jun 3, 2013, at 9:56 AM, Sorin Burjan <[email protected]> wrote:
Hello Vincent,
On Fri, May 31, 2013 at 4:53 PM, Vincent Massol <[email protected]> wrote:
Hi Sorin,
On May 31, 2013, at 3:16 PM, Sorin Burjan <[email protected]> wrote:
Hello everybody,
After several months of fragmented work, I have finally managed to complete the next iteration of Test Report Application [1]. Final parts of the code will be committed next week. Taking into consideration the feedback I received, I implemented several changes into the application to make it more user friendly and robust.
In order to put the application in production, Manuel and me converted the Manual Test Report Template [2] into Test Cases to be used by the Test Report Application. These test cases are committed on Github [3]. Now we have 404 Test Cases, grouped in 22 Spaces as follows: 1) Action Menus Tests 2) App Within Minutes Tests 3) Dashboard Macro Tests 4) Page Tabs Tests 5) Rights Tests 6) Tags Tests 7) Wiki Editor Tests 8) WYSIWYG Editor Tests 9) Activity Stream Tests 10) Blog Tests 11) Document Index Tests 12) Panels Tests 13) Search Tests 14) User Profile Tests 15) Wiki Manager Tests 16) Administration Tests 17) Color Themes Tests 18) Jump To Page Tests 19) Register and Authentication Tests 20) Space Macro Tests 21) User Status Tests 22) Workspaces Tests
It would be nice to have a one to one mapping between these categories to maven modules. That will make it much easier to maintain.
I am not sure I quite understand what you mean with this. You want me to move each space to its own maven module ? I don't understand what are the advantages.
No. I'm suggesting to keep the existing taxonomy: https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core
Thanks -Vincent
Regards, Sorin B.
My proposal is that we create a dedicated subwiki for this, qa.xwiki.orgwhere we will deploy the application + test cases. The rationale behind having a dedicated subwiki for this is that we don't want to crowd an already existing subwiki with the test cases and also the spaces which will hold the test execution pages.
WDYT ? I am waiting for your opinions/concerns/questions about this.
ok for a dedicated wiki but I'm concerned about its name. If we name it "qa" it means it's going to be used for all QA, i.e. we'll need to move
QA
pages from dev.xwiki.org to it. I'm not sure we want this from what you describe. So a name like "test.xwiki.org" seems a better name to me.
Thanks -Vincent
Regards, Sorin B.
[1] https://github.com/xwiki-contrib/application-testreporting [2]
http://www.xwiki.org/xwiki/bin/view/TestReports/ManualTestReportTemplate
[3] https://github.com/xwiki-contrib/application-testreporting-cases
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (3)
-
Daniel Patriche -
Sorin Burjan -
Vincent Massol