Partner – DBSchema – NPI EA – (tag = SQL)
DbSchema is a super-flexible database designer, which can take you from designing the DB with your team all the way to safely deploying the schema.
The way it does all of that is by using a design model, a database-independent image of the schema, which can be shared in a team using GIT and compared or deployed on to any database.
And, of course, it can be heavily visual, allowing you to interact with the database using diagrams, visually compose queries, explore the data, generate random data, import data or build HTML5 database reports.
>> Take a look at DBSchema
Partner – CAST AI – NPI EA (tag = kubernetes)
The Kubernetes ecosystem is huge and quite complex, so it’s easy to forget about costs when trying out all of the exciting tools.
To avoid overspending on your Kubernetes cluster, definitely have a look at the free K8s cost monitoring tool from the automation platform CAST AI. You can view your costs in real time, allocate them, calculate burn rates for projects, spot anomalies or spikes, and get insightful reports you can share with your team.
Connect your cluster and start monitoring your K8s costs right away:
>> FREE Kubernetes cost monitoring
Partner – MongoDB – NPI EA (tag = MongoDB) Partner – Thundra – NPI EA (tag = Jenkins)
You can get some real insight into your CI pipelines, and into your tests by using Foresight.
This includes not just the basics but some actual, actionable data like Change Impact Analysis, where we can see the changes in a PR and correlate them to test runs and test coverage to show how they affect our builds:
>> Try out Foresight in a project
This to-the-point tutorial describes the failsafe plugin, one of the core plugins of the Maven build tool.
For an overview of the other core plugins, refer to this article.
2. Plugin Goals
The failsafe plugin is used for integration tests of a project. It has two goals:
- integration-test – run integration tests; this goal is bound to the integration-test phase by default
- verify – verify that the integration tests passed; this goal is bound to the verify phase by default
3. Goal Execution
This plugin runs methods in test classes just like the surefire plugin. We can configure both plugins in similar ways. However, there're some crucial differences between them.
First, unlike surefire (see this article) which is included in the super pom.xml, the failsafe plugin with its goals must be explicitly specified in the pom.xml to be part of a build lifecycle:
The newest version of this plugin is here.
Second, the failsafe plugin runs and verifies tests using different goals. A test failure in the integration-test phase doesn't fail the build straight away, allowing the phase post-integration-test to execute, where clean-up operations are performed.
Failed tests, if any, are only reported during the verify phase, after the integration test environment has been torn down properly.
In this article, we introduced the failsafe plugin, comparing it with the surefire plugin, another popular plugin used for testing.
The complete source code for this tutorial can be found over on GitHub.
res – Maven (eBook) (cat=Maven)