This article is a presentation of a new little framework, I have developed and used on several projects.
The framework is for Spring Framework and requires Java 8.0. The code is on GitHub and downloadable from Bintray or JCenter.
This is a simple example of code to demonstrate how to use the library fakesmtp-junit-runner to write integration tests with mail servers.
The library has been released on GitHub and Maven Central. Continue Reading
A Dashboard can be a very efficient communication tool for a team, between managers and business units. It enables an organization around a vision to share common goals. It can also be useful to identify weaknesses in processes and adapt your strategy according to them.
This article is showing you how to use SonarQube with ReactJS and its JSX files. I will use both SonarQube JavaScript plugin and the additional plugin Sonar EsLint plugin.
In this article, I will present you two new SonarQube plugins that you will never find on SonarQube marketplace (for some good reasons).
Keep reading if you are developing in TypeScript, AngularJS 2, Javascript.
Today, I released a new library to help developers to write integration tests with mail servers.
The library has been released on GitHub and Maven Central.
Links : github.
Important : Part of the source code of this library has been modified and adapted from the project of FakeSmtp. I want to thank him since his project inspired me the creation of that library.
This library is an extension to JUnit to allow developers to write integration tests where a SMTP server is required.
The how-to is quite simple :
The project requires JUnit 4.11 or higher. It also requires SLF4J API presents in the classpath. I did not bundle them in the library to avoid conflicts.
To use it, adds the library to your maven or gradle config script :
For maven :
<dependency>
<groupId>com.github.sleroy</groupId>
<artifactId>fakesmtp-junit-runner</artifactId>
<version>0.1.1</version>
<scope>test</scope>
</dependency>For gradle :
testCompile "com.github.sleroy:fakesmtp-junit-runner:0.1.1"Step 1 :
Creates a JUnit test :
public class SmtpSendingClassTest {
@Test
public void testCase1() {
}
}Step 2 :
Adds the new Junit rule with its configuration :
public class SmtpSendingClassTest {
@Rule
public FakeSmtpRule smtpServer = new FakeSmtpRule(ServerConfiguration.create().port(2525).charset("UTF-8"));
@Test
public void testCase1() {
}
}Step 3 :
You are ready to use it, controls the mailbox or the server state :
Assert.assertTrue(smtpServer.isRunning());public class SmtpSendingClassTest {
@Rule
public FakeSmtpRule smtpServer = new FakeSmtpRule(ServerConfiguration.create().port(2525).charset("UTF-8"));
@Test
public void testCase1() {
Assert.assertTrue(smtpServer.isRunning());
Assert.assertTrue(smtpServer.mailbox().isEmpty());
}
}
I have tried Vue.js and just love it.
Some weeks ago, I started a new project for which, I have to build an internet website.
After spending really long hours on internet, browsing, collecting every possible testimonials and advices and comparing them to my first impressions, I decided to start with an hybrid / multiple page site.
(if you are interested by the reasons, it will be the subject of another post).
An hybrid /multiple page site is a website where the content is rendered both from server side and client side at the opposition of single page application (SPA) full client side and a classical server side site(PHP..) Since I want to use the power of modern Js Frameworks as double binding, refreshing, Ajax widgets, Es2016, reactive programming and somewhat control which pages needs to be reloaded, I had to make a choice.
The list of choice is somewhat limited if keep only the 5 most popular ones. (yes I am resolutely not a pioneer of the JavaScript Jungle)
I made the following list :
I defined some selection criteria besides the popularity :
No code bloat : specifically to JavaScript, the syntax and the missing OOP native programming have been producing many frameworks with dumb syntax without any semantical and often syntaxical meaning. To overcome the limitations, many frameworks are using syntax sugar, making them a nightmare to memorize. The most ridiculous is the attempt to stick on these syntaxical blobs, some pseudo theorical terms.
A good framework should offer different levels of usages from the straightforward approach to build quickly and easily a website with the common use cases to the low-level approach where the experimented developer is able to tune the required details. What has been done in Laravel, Spring framework or Symphony are good samples.
Symphony framework is known as a huge galaxy. Many components, industry quality grade, but an overwhelming complexity if you start head on.
Therefore they have created a micro — framework called Silex to bootstrap an PHP application without the nasty details and it is deadly simple. If you want more complex things, the components behind Silex are the Symphony ones.
For a web framework, always study how do they handle forms. Especially a basic post form. It takes five minutes in plain HTML to build an (unsecured) form. How long does it take with this framework?
The same thing works for **Spring* and Spring boot.
The framework must have a business friendly licence. No doubt, no legal restriction for the future company. (by the way do you know you cannot build weapons software in Java, please stick to the line…)
An extensible / plug-ins architecture. I believe the success of a framework resides in the possibility to enable the necessary functionalities (aka feature toggling) during your project. Authentication, reactive programming, lazy loading, modularity.
Based on these selection criteria, here is my evaluation.
Disclaimer: I have a highly respect for the guys who wrote these frameworks and I do not doubt of their outstanding skills. AngularJS
I have experienced projects with AngularJS and I renounced since it is a deprecated technology. Too much code bloat, slow (I should rather say hard-to-tune) and all efforts are concentrated on the new Angular framework. Also, I think I could have a problem with my use case and disabling the AngularJS router.
Angular 2: I have received a training in January and wrote several prototypes since. I have been a huge fan of typescript, angular-cli. I was happy and thinking, they took the best ideas from the other frameworks and build a big melting pot.
Angular : melting pot
In Angular, you will find web components, uses template a la React.js, you have opt-in double binding, directives, modular architecture, lazy loading and so on and so on. But I progressively hate Angular for many details, slowing me down in my developments.
I really dislike their API and concepts to build forms. You have two choices, a template form design and programmatic form design. The first one is almost useless and the second one is deadly cumbersome.
In Angular, they decided to kill HTML and recreate it. How? Case-sensitive attributes and non HTML attributes. You cannot use your normal code editor on it. Beautifier tools not works or partially works. And worse of all, they conceive this awful syntax based on brackets, parens, Well, I think their are huge practitioners of the Brainfuck language.
Brainfuck language
The last issue I encountered is with their wish to produce an industrial, scalable (in the sense if I put more developers on my project, I maintain a stable learning and complexity curve). Yes, they provide dependency injection, IOC. But it really increases the learning curve.
I really wanted to start with React.js. As far I have studied it, the framework seems full of promises, with some nice pluggable functionalities.
However at the time I began to use it, I received a lot of news. The concern is about the React.js license, the Facebook license (link1, link2, link3).
Since there is a threat for the future business (everything can be considered as a social network after all), I have rejected it.
I have never tried Ember.js. Based in my readings, the framework is definitely worth of attention to build SPA applications but not for my use case. Note : during the writing of this post, I felt on that link, confirming that maybe I was wrong about ember.js
On Twitter, I am receiving a lot of feedback from happy users of Vue.js and I decided to give a try.
The syntax seems deadly simple.
Here is the brief of my experience :
I did not use vue-cli, I had to create my own packaging to adapt Vue.js to multipage architecture.
Code bloat: the Vue.js framework is really simple and the documentation quite good. The documentation for the plug-in vue-loader is quite good but I really hate the webpack syntax to enable it (rant..)
Learning curve: I did not try the most hard-core functionalities of Vue.js, though I am using vue-loader, a different template renderer (pug), transitions, a little bit components and lazy loading.
My biggest difficulty have been to maintain my js bundle as low as possible by producing chunks.
The second issue has been to understand why creating a view was creating an App and my component below using the render() function. However I think that Vue.js is easier than Angular. 2.
As in the previous example, the syntax is quite straightforward, no need to learn complex concepts to begin with.
The framework is also compatible with Typescript and the logic behind is quite simple.
Vue.js can be extended with several plug-ins and functionalities. I did not try all of them and the fact you are enabling them manually is comforting me in my approach.
Vue.js is not enforcing a particular programming paradigm(IOC, interfaces, Reactive programming, or. RxJS).
The only reproach I could formulate is a little fear about the Vue.js ecosystem. Please integrate existing libraries rather trying to recreate or mimic ReactJS libraries.
In conclusion, both of these frameworks are legitimate and have their lot of practitioners, and I don’t blame it. Vue.js has been my choice and I do not regret it, yet, since it has made my project easy, fun and effective.
I will try to provide more feedback in the following weeks especially on form editing, unkt testing and E2E testing.
Thanks for your attention
In this short story, I will relate how I migrate my blog personal website from a classic VM instance to a container using Google Cloud Container Engine and Kubernetes, Docker, Nginx.
Thanks to its popularity, Docker has disrupted many companies and blurred the silos between Developers and Operations. In this article, based partially on my own experiences.
As many other markets, the SQA/ALM Market soon will meet #disruption. Domains like machine learning, deep learning and cloud computing will force it to evolve in the next few years. This article is presenting some predictions about the future of the quality tools.