| [alf-req] POC Build/Deploy/Test Use Case |
|
Hello Alfers, I have a few questions about the POC Demo Build/Deploy/Test use
case. The use case goal appears to be the fully automated
transition from build approved to test build complete state. However, a
precondition must exist for this to occur: the mapping from the build project to the Segue Test
Manager tests to be run after each build. It is my understanding that Segue’s Test Manager
currently does not support this type of persistent mapping. For example, a build project
may have 50 test definitions associated with it. The user must then manually select
which subset of the 50 definitions to run. This mapping via user selection is not
persistent as a "default test after build" subset within Segue’s Test Manager. Since there was not a “user selects build project to build
tests mapping” action in the use case, Is the intent to store a fixed mapping in a config
file? How should the build project to build tests mapping be done in the POC demo? I assume there is no scheduling
requirement for these demo tests ( tests x1, x2 get queued once and run immediately;
tests y and z scheduled for 2am every day, etc.). Segue can implement scheduling of POC build
tests as they see fit. Again, the main goal of the POC is to demonstrate the fully automated transition
of build/deploy/test states. There are no fine-grained requirements on build tests, such
as scheduling. Thanks, Bob Bob Brady, Ph.D. Senior Software Engineer Segue Software 201 Spring Street t: 781-402-5975 f: 781-402-1097 w: www.segue.com |