theprojecter / spectacular Goto Github PK

What steps will reproduce the problem?
1.  Execute Spectacular with any options

What is the expected output? What do you see instead?

Log message output is:

> Spectacular -eucBasePackage (anything)  
2009-11-20 10:36:30,654 [main] INFO 
minderupt.spectacular.spine.SpectacularSpine - Starting compono spine!

The last line should say "tarting Spectacular spine!"

Executable use cases are not styled with colors, i.e. red background for
failed steps, yellow for pending, etc.

What steps will reproduce the problem?
1.  Write EUC in Sharepoint.  No BDD tables
2.  Execute spectacular on document using remote path (i.e. http://)
3.  Spectacular fails with NPE:

C:\SpectacularPOC>Spectacular -projectXml .\teamworks_project.xml
2010-01-06 12:47:45,984 [main] INFO 
minderupt.spectacular.spine.SpectacularRunn
er - Loading Project XML: .\some_project.xml
2010-01-06 12:47:45,984 [main] INFO 
minderupt.spectacular.spine.ProjectFileOpti
onsAdapter - Parsing project XML
2010-01-06 12:47:46,140 [main] INFO 
minderupt.spectacular.spine.ProjectFileOpti
onsAdapter - # of specs:  3
2010-01-06 12:47:46,140 [main] INFO 
minderupt.spectacular.spine.ProjectFileOpti
onsAdapter - Options loaded for spec:  http://somespec.com/some/spec.html
2010-01-06 12:47:46,140 [main] INFO 
minderupt.spectacular.spine.SpectacularRunn
er - Iterating through options...
2010-01-06 12:47:46,140 [main] INFO 
minderupt.spectacular.spine.SpectacularRunn
er - Doing spec:  http://somespec.com/some/spec.html
2010-01-06 12:47:46,156 [main] INFO 
minderupt.spectacular.spine.SpectacularRunn
er - Configuring Spine
2010-01-06 12:47:46,812 [main] INFO 
minderupt.spectacular.spine.SpectacularRunn
er - Setting user-specified Document Reader:  httpDocumentReader
2010-01-06 12:47:46,812 [main] DEBUG
minderupt.spectacular.spine.SpectacularSpin
e - Starting Spectacular spine!
2010-01-06 12:47:46,812 [main] DEBUG
minderupt.spectacular.spine.SpectacularSpin
e - Loading specification from http://somespec.com/some/spec.html
2010-01-06 12:47:49,265 [main] DEBUG
minderupt.spectacular.spine.SpectacularSpin
e - Parsing specification and extracting artifacts.
2010-01-06 12:47:49,422 [main] DEBUG
minderupt.spectacular.spine.SpectacularSpin
e - Figuring out what types of artifacts we have.
Exception in thread "main" java.lang.NullPointerException
        at
minderupt.spectacular.decisioner.bdd.JBehaveBDDKeywordDecisioner.deci
sion(JBehaveBDDKeywordDecisioner.java:24)
        at
minderupt.spectacular.decisioner.ChainedDecisionerAgent.decide(Chaine
dDecisionerAgent.java:44)
        at
minderupt.spectacular.spine.SpectacularSpine.run(SpectacularSpine.jav
a:72)
        at
minderupt.spectacular.spine.SpectacularRunner.main(SpectacularRunner.
java:60)




What is the expected output? What do you see instead?

Should not NPE on this


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1.  Run Spectacular against Executable Use Cases with some steps not
implemented
2.  Notice (NOT PERFORMED) steps have a black background in the report.

What is the expected output? What do you see instead?
By default the background should be white for (NOT PERFORMED)

Any details of backlog item:

What steps will reproduce the problem?

1. Run Spectacular
2. The only way to include test fixtures in classpath is to specify it in
CLASSPATH_PREFIX env variable, which isn't ideal.

What is the expected output? What do you see instead?

1. Add a parameter to the command line which would add test fixtures and
any other supporting libraries to the classpath


Please use labels and text to provide additional information.

Upload source code to google code, release v1 beta

What steps will reproduce the problem?
1.  Run EUC test through Spectacular
2.  Force one of the @Flow steps to fail by throwing RuntimeException
3.  The following steps still execute

What is the expected output? What do you see instead?

All steps after the failure should be marked NOT PERFORMED and not actually
be executed.


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1.  Execute EUC table, where a USER ACTION is "PENDING" and there is an
expectation immediately following, i.e.:

| User Action | Expectation |
| User does something | User expects Something |
| User does something else | User expects something else |

2.  Once the initial USER ACTION is pending, the expectation immediately
following is not printed out in the test results, i.e.:

| User Action | Expectation |
| User does something (PENDING) |  |
| User does something else (NOT PERFORMED) | User expects something else
(NOT PERFORMED) |

What is the expected output? What do you see instead?

The expected results is:

| User Action | Expectation |
| User does something (PENDING) | User expects Something (NOT PERFORMED) |
| User does something else (NOT PERFORMED) | User expects something else
(NOT PERFORMED) |




Please use labels and text to provide additional information.

What steps will reproduce the problem?
1.  Execute Spectacular with no arguments (i.e. > Spectacular )

What is the expected output? What do you see instead?

It should run with default options (no EUC base packages?) and/or display
required command line arguments and then exit gracefully.

Any details of backlog item:

Change Maven2 POM groupId and artifactId to reflect common standards:

groupId: com.minderupt.spectacular
artifactId: spectacular-core
version: whatever

Do this before things get too crazy, as changing the pattern gets more
difficult with time.

What steps will reproduce the problem?
1. Run spectacular with an executable use case, output report to file system
2. View report file
3. Notice that the headers (i.e. User Action, Expectation, etc) are not
output in the report

What is the expected output? What do you see instead?
I expect to see the report as written in the original spec

2010-01-06 15:16:01,720 [main] INFO 
minderupt.spectacular.executor.agent.Linear
ArtifactExecutorAgent - Executing artifact type:  BDD
2010-01-06 15:16:01,720 [main] INFO 
minderupt.spectacular.executor.bdd.JBehaveA
rtifactExecutor - Loading step class:  blah.bdd.WhateverTest
2010-01-06 15:16:01,735 [main] ERROR
minderupt.spectacular.executor.bdd.JBehaveA
rtifactExecutor - Unable to load step class: blah.bdd.WhateverTest
java.lang.ClassNotFoundException: blah.bdd.WhateverTest
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClassInternal(Unknown Source)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Unknown Source)
        at
minderupt.spectacular.executor.bdd.JBehaveArtifactExecutor.executeArt
ifact(JBehaveArtifactExecutor.java:38)
        at
minderupt.spectacular.executor.agent.LinearArtifactExecutorAgent.exec
uteArtifacts(LinearArtifactExecutorAgent.java:45)
        at
minderupt.spectacular.spine.SpectacularSpine.run(SpectacularSpine.jav
a:86)
        at
minderupt.spectacular.spine.SpectacularRunner.main(SpectacularRunner.
java:60)
Exception in thread "main" java.lang.NullPointerException
        at
minderupt.spectacular.executor.agent.LinearArtifactExecutorAgent.exec
uteArtifacts(LinearArtifactExecutorAgent.java:52)
        at
minderupt.spectacular.spine.SpectacularSpine.run(SpectacularSpine.jav
a:86)
        at
minderupt.spectacular.spine.SpectacularRunner.main(SpectacularRunner.
java:60)

C:\SpectacularPOC>

What steps will reproduce the problem?
1.  Create a project xml with an XML comment before the <spectacular> root node
2.  Run Spectacular

Notice how it doesn't detect any specs?

What is the expected output? What do you see instead?
It should ignore comments and other whitespace nodes.  Bad parsing logic.

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1.  Execute spectacular without a -specLocation parameter

What is the expected output? What do you see instead?

Should exit gracefully asking for required parameters

Instead we see:

> Spectacular -eucBasePackage (anything) 
2009-11-20 10:36:30,654 [main] INFO 
minderupt.spectacular.spine.SpectacularSpine - Starting compono spine!
2009-11-20 10:36:30,656 [main] INFO 
minderupt.spectacular.spine.SpectacularSpine - Loading specification from null
Exception in thread "main" java.lang.NullPointerException
    at
minderupt.spectacular.reader.resource.SpringResourceBasedDocumentReader.read(Spr
ingResourceBasedDocumentReader.java:28)
    at minderupt.spectacular.spine.SpectacularSpine.run(SpectacularSpine.java:52)
    at
minderupt.spectacular.spine.SpectacularRunner.main(SpectacularRunner.java:63)

Expect the browser to be stop()'ed at the end of a test run.

BDD tests need to include new lines, colors, etc.

What steps will reproduce the problem?
1. Write EUC with a step that fails
2. Open report, go to step that fails


What is the expected output? What do you see instead?

If it is some type of exception, it should show the exception in addition
to more details about the failure, i.e.:

User selects "Reviews" link (FAIL)
java.lang.reflect.InvocationTargetException Caused by:
com.thoughtworks.selenium.SeleniumException: Timed out after 5000ms

What steps will reproduce the problem?
1. Run spectacular with ruby script that references lib like selenium
2.  Can't find lib
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

Too much output in INFO logging.  We can probably stop the INFO logging of
the document itself.

The EUC Executor is not written for extensibility and it is difficult to
find defects.  Must refactor (and increase unit test coverage)

What steps will reproduce the problem?
1.  Execute spectacular as such:
H:\>Spectacular -eucBasePackage com.minderupt.something -specLocation
"http://code.google.com/p/spectacular/wiki/ExampleSpec" -config
"c:/Spectacular-0.9-beta/config.xml"


What is the expected output? What do you see instead?
Spectacular is expecting a classpath param of some kind, I want to give it
a file location (or even remote if possible)