My First Post      My Facebook Profile      My MeOnShow Profile      W3LC Facebook Page      Learners Consortium Group      Job Portal      Shopping


Monday, April 13, 2020

maven surefire plugin runtime exception - writing xml report stdout/stderr

Problem: Sometimes you get the RunTime exception in your java projects. Example in an enterprise spring boot application when you use:

> mvn clean install
or, mvn package

See the error snapshot below:

Tests run: 325, Failures: 0, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  24:49 min
[INFO] Finished at: 2020-04-13T13:25:50+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project postbooking-ndc-pad: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: java.lang.RuntimeException: When writing xml report stdout/stderr: /var/folders/3r/wl3bcq6x0cq1_zxj94xtz6ww0000gn/T/stdout8283814721678605256deferred (No such file or directory) -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1]

Root cause:

This mainly happens because of using wrong/ old version of suefire in your pom.xml while some parts of your code requires higher versions in compilation.

Possible remediation:

1. Either ignore tests while building
>mvn install -DskipTests

2. or,  use latest Surefire in pom.xml 2.22.0

Wednesday, April 8, 2020

Story point Estimation guideline

A story point is a metric used in agile project management and development to estimate the difficulty of implementing a given user story, which is an abstract measure of effort required to implement it. In simple terms, a story point is a number that tells the team about the difficulty level of the story. Difficulty could be related to complexities, risks, and efforts involved.

Story point estimation, a kind of relative estimation, is typically performed at the Product Backlog Grooming Sessions and the Product Backlog is evaluated by the team who responsible for the actual development and testing work.

In most of the cases (and as defined by Scrum principles), the story pointing or estimation is done using some pre-decided base story. Every other story is pointed in respect to that story. However, if it is your first story or a new project, you can start with following simple chart.

Story points
Estimation effort
1< 1 day
32-3 days
53-5 days
85+ days
8+It is advised to break the story in simpler
Please note that this is what you do. Your style and the way your organization works might be slightly different. However, the basic idea remains the same. And the goal is also one - Success!

Cheers :)