angular-fullstack/generator-angular-fullstack

Add option to test phase to generate junit output

Open

#2066 opened on Jul 16, 2016

View on GitHub
 (1 comment) (1 reaction) (0 assignees)JavaScript (6,134 stars) (1,268 forks)batch import
DifficultHelp Wantedenhancementsemver-minor

Description

  • I understand that GitHub issues are not for tech support, but for questions specific to this generator, bug reports, and feature requests.
Item Version
generator-angular-fullstack 4.0.0
Node x.x.x
npm x.x.x
Operating System OS X 10 / Windows 10 / Ubuntu 15.10 / etc
etc etc
Item Answer
Transpiler Babel / TypeScript
Markup HTML / Jade
CSS CSS / LESS / SCSS / Stylus
Router ngRoute / ui-router
Build Tool Gulp
Client Tests Mocha
DB MongoDB / SQL
Auth Y / N
etc etc

It would be good to have a feature where the test phase can generate optional junit XML files e.g. gulp test:junit This would make the tests for the generator itself more visible to circleci https://circleci.com/docs/test-metadata/ which I think is the CI for v4.0.0 This would also help users of the generator as junit is a standard in Jenkins, Bamboo and TeamCity

I think the tricky part will be assembling the tests from all the temporary apps which are part of the testing

I looked into this as I need the tests to pass so circleci can go ahead and create a branch for the docker image https://github.com/angular-fullstack/generator-angular-fullstack/issues/1959

such as in circle.yml

## Deployments
deployment:
  docker:
    # update the upstream dockerfile after a push
    branch: [master, docker-integration]
    commands:
      - generator-angular-fullstack/angular-fullstack-dockerfile/create_branch.sh

Contributor guide

Tech stack
javascriptnodejs
Domain
testingci cd
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
GulpMochaJUnit XML
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate the existing Gulpfile to add a new task `test:junit`. Review how tests are currently run (likely using mocha) and configure mocha to output JUnit XML. Consider using a mocha reporter like 'mocha junit reporter'. The main challenge is aggregating test results from multiple temporary apps used in testing; explore solutions like running tests sequentially or using a script to combine outputs. Check the repo's CircleCI config in circle.yml for integration.