You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Brian Foster (JIRA)" <ji...@apache.org> on 2012/06/20 03:18:44 UTC
[jira] [Created] (OODT-468) Integration Test Infrastructure
Brian Foster created OODT-468:
---------------------------------
Summary: Integration Test Infrastructure
Key: OODT-468
URL: https://issues.apache.org/jira/browse/OODT-468
Project: OODT
Issue Type: Task
Affects Versions: 0.4
Environment: none
Reporter: Brian Foster
Assignee: Brian Foster
Priority: Minor
Fix For: 0.5
As OODT continues to mature, i think we are getting to the point where we need some kind of release integration check infrastructure that nominally will bring up all the components and execute some test runs on them... at first these tests will be run manually by engineers before each OODT release... thus encouraging them to automate them ;)... currently there is no way to prove a released version of OODT is any more a 'blessed' version of the code than any given checked out revision. I think having 'blessed' stable releases is important.
I'm thinking of creating 2 google docs. The first being a word document enumerating the scenarios which should be run. The second being a spreadsheet with a tab for each release enumerating which scenarios where run and whether or not passed (with a column for bug ID created if scenario fails). As each scenario gets automated, it can then be mark as such and only the none automated scenario will continue to be executed by engineers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-468) Integration Test Infrastructure
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401192#comment-13401192 ]
Chris A. Mattmann commented on OODT-468:
----------------------------------------
Thanks dude!
> Integration Test Infrastructure
> -------------------------------
>
> Key: OODT-468
> URL: https://issues.apache.org/jira/browse/OODT-468
> Project: OODT
> Issue Type: Task
> Affects Versions: 0.4
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.5
>
>
> As OODT continues to mature, i think we are getting to the point where we need some kind of release integration check infrastructure that nominally will bring up all the components and execute some test runs on them... at first these tests will be run manually by engineers before each OODT release... thus encouraging them to automate them ;)... currently there is no way to prove a released version of OODT is any more a 'blessed' version of the code than any given checked out revision. I think having 'blessed' stable releases is important.
> I'm thinking of creating 2 google docs. The first being a word document enumerating the scenarios which should be run. The second being a spreadsheet with a tab for each release enumerating which scenarios where run and whether or not passed (with a column for bug ID created if scenario fails). As each scenario gets automated, it can then be mark as such and only the none automated scenario will continue to be executed by engineers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OODT-468) Integration Test Infrastructure
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-468:
-----------------------------------
Component/s: build proces
> Integration Test Infrastructure
> -------------------------------
>
> Key: OODT-468
> URL: https://issues.apache.org/jira/browse/OODT-468
> Project: OODT
> Issue Type: Task
> Components: build proces
> Affects Versions: 0.4
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.5
>
>
> As OODT continues to mature, i think we are getting to the point where we need some kind of release integration check infrastructure that nominally will bring up all the components and execute some test runs on them... at first these tests will be run manually by engineers before each OODT release... thus encouraging them to automate them ;)... currently there is no way to prove a released version of OODT is any more a 'blessed' version of the code than any given checked out revision. I think having 'blessed' stable releases is important.
> I'm thinking of creating 2 google docs. The first being a word document enumerating the scenarios which should be run. The second being a spreadsheet with a tab for each release enumerating which scenarios where run and whether or not passed (with a column for bug ID created if scenario fails). As each scenario gets automated, it can then be mark as such and only the none automated scenario will continue to be executed by engineers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-468) Integration Test Infrastructure
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400111#comment-13400111 ]
Chris A. Mattmann commented on OODT-468:
----------------------------------------
heh, this sounds great Brian. Can you give me access to the spreadsheet?
> Integration Test Infrastructure
> -------------------------------
>
> Key: OODT-468
> URL: https://issues.apache.org/jira/browse/OODT-468
> Project: OODT
> Issue Type: Task
> Affects Versions: 0.4
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.5
>
>
> As OODT continues to mature, i think we are getting to the point where we need some kind of release integration check infrastructure that nominally will bring up all the components and execute some test runs on them... at first these tests will be run manually by engineers before each OODT release... thus encouraging them to automate them ;)... currently there is no way to prove a released version of OODT is any more a 'blessed' version of the code than any given checked out revision. I think having 'blessed' stable releases is important.
> I'm thinking of creating 2 google docs. The first being a word document enumerating the scenarios which should be run. The second being a spreadsheet with a tab for each release enumerating which scenarios where run and whether or not passed (with a column for bug ID created if scenario fails). As each scenario gets automated, it can then be mark as such and only the none automated scenario will continue to be executed by engineers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-468) Integration Test Infrastructure
Posted by "Brian Foster (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397204#comment-13397204 ]
Brian Foster commented on OODT-468:
-----------------------------------
Scenarios Document:
https://docs.google.com/document/d/1D020Pm9rJeGasknAyr8rMORG9j4Z1_a4J4ZMHYXXiwU/edit
Release Testing Spreadsheet:
https://docs.google.com/spreadsheet/ccc?key=0AhJdNnP8nCpLdGdmdTZDaUV1ZmQ2V3g5cmlMZlJ5R3c
Please just hit me up (bfoster@apache.org) if you would like to get write permission to these files.
> Integration Test Infrastructure
> -------------------------------
>
> Key: OODT-468
> URL: https://issues.apache.org/jira/browse/OODT-468
> Project: OODT
> Issue Type: Task
> Affects Versions: 0.4
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.5
>
>
> As OODT continues to mature, i think we are getting to the point where we need some kind of release integration check infrastructure that nominally will bring up all the components and execute some test runs on them... at first these tests will be run manually by engineers before each OODT release... thus encouraging them to automate them ;)... currently there is no way to prove a released version of OODT is any more a 'blessed' version of the code than any given checked out revision. I think having 'blessed' stable releases is important.
> I'm thinking of creating 2 google docs. The first being a word document enumerating the scenarios which should be run. The second being a spreadsheet with a tab for each release enumerating which scenarios where run and whether or not passed (with a column for bug ID created if scenario fails). As each scenario gets automated, it can then be mark as such and only the none automated scenario will continue to be executed by engineers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-468) Integration Test Infrastructure
Posted by "Brian Foster (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400912#comment-13400912 ]
Brian Foster commented on OODT-468:
-----------------------------------
done!
> Integration Test Infrastructure
> -------------------------------
>
> Key: OODT-468
> URL: https://issues.apache.org/jira/browse/OODT-468
> Project: OODT
> Issue Type: Task
> Affects Versions: 0.4
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.5
>
>
> As OODT continues to mature, i think we are getting to the point where we need some kind of release integration check infrastructure that nominally will bring up all the components and execute some test runs on them... at first these tests will be run manually by engineers before each OODT release... thus encouraging them to automate them ;)... currently there is no way to prove a released version of OODT is any more a 'blessed' version of the code than any given checked out revision. I think having 'blessed' stable releases is important.
> I'm thinking of creating 2 google docs. The first being a word document enumerating the scenarios which should be run. The second being a spreadsheet with a tab for each release enumerating which scenarios where run and whether or not passed (with a column for bug ID created if scenario fails). As each scenario gets automated, it can then be mark as such and only the none automated scenario will continue to be executed by engineers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira