react testing
Posted: June 21, 2017 Filed under: programing | Tags: enzyme, jest, reactjs, sonar, sonarcloud.io, SonarQube, tests, travisci Leave a commentI have to say that hardest part with react was to figure out testing. (testing components is easy with thousands examples). But how to test props, state vlaues, clicking events, helping functions,… There are many projects in github and almost all of them are without any tests.
I have put together small app, where you can find code with tests.
I have tested:
* components
* props values
* state values
* events on components like clicking,…
* functions
Frankly I haven’t seen any project where they would cover all of the above.
I am not gonna write step by step, just small info I am using Jest & Enzyme testing framework.
For details better check my code. Check for package.json for packages I am using and __tests__ folders for tests.
Here are:
* github link
* travis link
* sonarcloud.io link
enjoy
node/react -> github -> travis -> sonar
Posted: June 16, 2017 Filed under: programing | Tags: node, reactjs, sonar, sonarcloud.io, SonarQube, travisci Leave a commentWhen programming I like to keep my code as clean and automated as possible.
I like sonar (does analysis on your code and provide you output how many duplicate, code smells, unused variables,..)
I like node.js / react.js for its quick prototyping and agile and others advantages. So lastly I was looking if I can have setup where I could automate my infrastructure code -> push to VCS (github) -> CI (travis) -> code analysis (Sonar).
Here are steps what you need to do:
- github.com -> on project settings turn on “travis-ci” integration
- github.com -> project -> settings -> Integration & services -> Add Service -> Travis CI
- travis-ci.com -> make sure after code push code build is triggered
- how to setup travis for sonar
- only thing I did in travis was to define SONAR_TOKEN variable (see above for details)
- sonarcloud.io – get started
- project:
.travis.yml
dist: trusty
sudo: required
addons:
sonarqube:
organization: "czechsource"
branches:
- master
- develop
jdk:
- oraclejdk8
script:
- sonar-scanner
cache:
directories:
- '$HOME/.sonar/cache'
sonar-project.properties
sonar.projectKey=czechsource:reactBlog
sonar.projectName=React.js blog
sonar.projectVersion=1.0
sonar.sources=src
sonar.language=js
sonar.sourceEncoding=UTF-8
sonar.branch=develop,master
Make sure you define sonacloud.io organization and token and use it in travis.
Update: I am using git flow and find out that branches “develop” were not sent to sonar. Make sure you add them in .travis.yml as well as in sonar-project.properties files (marked them in bold)
Update2: there is another option using sonarqube-scanner-node project . (I am assuming your project is made by create-react-app by facebook)
yarn add sonarqube-scanner-node --dev
yarn test -- --coverage
- package.json -> add in script section:
"sonarqube": "sonarqube-scanner-node"
- from command line:
yarn sonarqube -Dsonar.host.url=https://sonarcloud.io -Dsonar.organization=chowanioksource -Dsonar.sources=src -Dsonar.projectKey=chowanioksource:reactBlog -Dsonar.login=<sonarcloud.io token>
java 8 using jboss5
Posted: July 29, 2015 Filed under: java, programing | Tags: java, jboss5, jdk8 Leave a commentIf you need to run your app on jboss5 and using jdk8 you will get error
3:53:10,693 ERROR [AbstractKernelController] Error installing to Instantiated: name=AttachmentStore state=Described java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[java.net.URI] actual=[java.io.File] at org.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors(ReflectionUtils.java:395) at org.jboss.reflect.plugins.introspection.ReflectionUtils.newInstance(ReflectionUtils.java:153) at org.jboss.reflect.plugins.introspection.ReflectConstructorInfoImpl.newInstance(ReflectConstructorInfoImpl.java:106) .....
You need to modify “profile.xml” and add class=”java.io.File” into paramater element
<bean name="AttachmentStore" class="org.jboss.system.server.profileservice.repository.AbstractAttachmentStore">
<constructor>
<parameter class="java.io.File">
<inject bean="BootstrapProfileFactory" property="attachmentStoreRoot" />
</parameter>
</constructor>
Git house cleaning
Posted: June 29, 2015 Filed under: Linux, programing | Tags: delete remote branches, git, git flow Leave a commentI use *Git* for several years and there are tons of articles out there about how to create new branch, pull, fetch, merge, conflict resolve, etc…
I looked at how we are doing with branches on current project – holds over 1M of code lines and +10 years of its history – I was surprised that we had almost 2 000 branches (features, patches,….). We don’t follow the standard git flow (yeah I know we should, but some in our team thinks that for current project it is better how we do it now). So as you can see there are many branches which needs to be cleaned up and GIT helps a lot with that.
Some Git commands which are useful for cleanup:
Clean of local branches which has been deleted on remote server:
git fetch --prune
list of all branches (local & remote )
git branch --all
List branches which are merged to remote master:
git branch --all --merged origin/master
Result of above command can be deleted
Delete local branch:
git branch -d branch_name
Delete branch from remote “origin” :
git push origin --delete branch_name
Show list of branches which are not merged into remote master branch:
git branch --all --no-merged origin/master
Results from above command are not merged into master. You need to check whether those branches are new feature/patch branches (still in work in progress) or they were not merged because you feature/patch is not needed any more (absolete and can be deleted) or you simply forget to merged them into your master (which should not happen by using tools like “git flow”)
You can scripts to combine of commands together. Let’s say we want to see last commit day and author to find out whether branch is still under development or not.
for branch in `git branch -r --merged origin/master | egrep -v 'HEAD|master'`; do echo -e `git show --format="%ci %cr %an" $branch | head -n 1` \\t$branch; done | sort -r
Similarly you can create scripts, which deletes not used merged branches and many other things you need.
Running Docker on CentOS – accesing internet from docker
Posted: November 18, 2014 Filed under: Linux, programing, Uncategorized | Tags: centos, docker, ipv4 forward, network Leave a commentBy default your docker can’t reach to internet only to get centOS.
running this command solves the problem:
sysctl net.ipv4.ip_forward=1
unable to find valid certification path to requested target
Posted: March 13, 2014 Filed under: java, Linux, programing | Tags: certificate, InstallCert.java, java, jenkins, jssecacerts, keystore, sonar, SonarQube, ssl Leave a commentIt is always preferred to use https instead of http (specially when using passwords and so on…)
We have switched our SonarQube (tool for Continuous Inspection of code quality) to use https for security reasons. Anyway I have noticed that Jenkins stop sending new quality codes to our sonar. When I have checked the logs I have seen this stacktrace:
Exception in thread "main" java.lang.IllegalStateException: Fail to request server version at org.sonar.runner.Bootstrapper.getServerVersion(Bootstrapper.java:73) at org.sonar.runner.Runner.checkSonarVersion(Runner.java:220) at org.sonar.runner.Runner.execute(Runner.java:150) at org.sonar.runner.Main.execute(Main.java:84) at org.sonar.runner.Main.main(Main.java:56) Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1584) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:848) at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:106) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:877) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1089) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1116) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1100) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:402) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:166) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:951) at java.net.URLConnection.getContent(URLConnection.java:682) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getContent(HttpsURLConnectionImpl.java:406) at org.sonar.runner.Bootstrapper.remoteContent(Bootstrapper.java:125) at org.sonar.runner.Bootstrapper.getServerVersion(Bootstrapper.java:71) ... 4 more
So here you can see that Jenkins has problem to “handshake” ssl certificate.
follow these steps:
Download InstallCert.java
Search google – it originally was done in Sun, but you can find this program on google codes or somewhere else. You can even download binaries of this file.
Add Trusted Keystore
Run “InstallCert.java” on server (where you run your https service). something like java InstallCert localhost:443 -> press “1” when asked. It will add your “localhost” as a trusted keystore, and generate a file named “jssecacerts“.
[user@sonar ~]$ java InstallCert localhost:443 Loading KeyStore /usr/java/jdk1.6.0_37/jre/lib/security/cacerts... Opening connection to localhost:443... Starting SSL handshake.. Server sent 1 certificate(s): 1 Subject CN=Unknown, OU=Unknown, O=Vendavo, L=Unknown, ST=Czech republic, C=CZ Enter certificate to add to trusted keystore or 'q' to quit: [1] 1 Added certificate to keystore 'jssecacerts' using alias 'localhost-1'
I have removed most of the parts but the main parts are here:
a) press 1 when assked – you agree to add certificate for this domain into keystore
b) it created jssecacerts file
Verify Trusted Keystore
Run same command again 🙂 (this is full export – removed hashed data)
[mchowaniok@sonar ~]$ java InstallCert sonar.vmcz.vendavo.com:443 Loading KeyStore jssecacerts... Opening connection to sonar.vmcz.vendavo.com:443... Starting SSL handshake... No errors, certificate is already trusted Server sent 1 certificate(s): 1 Subject CN=Unknown, OU=Unknown, O=Vendavo, L=Unknown, ST=Czech republic, C=CZ Issuer CN=Unknown, OU=Unknown, O=Vendavo, L=Unknown, ST=Czech republic, C=CZ sha1 md5 Enter certificate to add to trusted keystore or 'q' to quit: [1] q KeyStore not changed
Copy jssecacerts
copy jssecacerts file into java/jre/lib/security folder (I had to done it under sudo )
[user@sonar ~]$ sudo cp jssecacerts /usr/java/default/jre/lib/security/
Done
verify it 🙂 in my case, run Jenkins job and verify data are uploaded to Sonar.
What lessons to learn from Mount Blanc and diving as software architect
Posted: December 28, 2013 Filed under: life, programing | Tags: developing, diving, hiking, problems, software architect Leave a commentIn my previous post about exceeding my limits I have mentioned 2 trips from several I did in 2013. I would like to share lessons I learnt specially for development. You will see that there is not much difference in mistakes in software development as well in mistakes in diving or reaching top of mountains.
Let’s share some problems we have encounter:
During descent from Mount Blanc we (group of 3 people) decided we are not going to be tight together anymore, as it give us more freedom and we don’t have wait on each other. On the way back one of my friend felt over the cliff and by miracle was lucky to not fall down in gulf. We can’t say same about his DLSr camera. We have lost our best pictures from ascent and top of Mount Blanc, anyway my friend is still with us enjoys life like never before.
During my so far most deep dive, we swum almost all time against current and we have spent more air than we thought. On the way up, we had to use extra safety air bottles we left in case of emergency, because we run out of air in our bottles.
These things I don’t share with everyone usually, because instead of learning lessons from my mistakes it scares them to actually not do anything.
And how it connects with development ?
- If possible do pair programming and TDD – best exercise can be learnt on coderetreat
- Never ever in name of “freedom, not enough time, not enough budget,…” write code without tests – tests are your safety “rope” which holds your code together and can saves you life
- Always count on unexpected events (have extra hours, budget, resource hidden which you can pull on when needed) – this is like having extra safety bottles with air in water
- Did you notice that both situation happened after “reaching goal” on the way back ? – Finishing your software and putting into production is our main goal, but be ready to expect the “real” problems when real users starts using it
- Good preparation is the key for success – be tough on yourself – think about the most worst cases and expect even worse situations
These are just few things – happy new year 2014 and be ready to exceed your limits in next coming year.
Jenkins on openshift #3 – building repo from github or bitbucket
Posted: December 16, 2013 Filed under: java, Linux, Mac, programing | Tags: bitbucket, git, github, jenkins, openshift, SonarQube, ssh Leave a commentNext task I wanted to do is to create jenkins on openshift and be able to build projects from github or bitbucket. It sounds simple, but you will face quite a lot of issues. So let’s do it:
Create Jenkins gear
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rhc create-app jenkins jenkins-1 "https://cartreflect-claytondev.rhcloud.com/reflect?github=majecek/openshift-community-git-ssh" |
- this creates gear called “jenkins” using jenkins-1 application and includes ssh wrapper “git-ssh” which helps you to overcome ssh obstacles (openshift forbids to write into .ssh folder) – as you will see we will have to solve this problem several times later as well
Set jenkins slave
jenkins needs other linux machines (called slaves) to use them for building, anyway we don’t have so much free gears, so we will use jenkins itself for it.
Manage Jenkins -> Configure System -> # of executors = 1 Labels = put here anything
Generate ssh key
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cd app-root/data/git-ssh/ | |
ssh-keygen (name your key as id_rsa – git-ssh will look there for it) | |
and set full path for new key (i.e. /var/lib/openshift/52ab37d0500446f3d30000ee/app-root/data/git-ssh/id_rsa) |
Add public key (id_rsa.pub) to github & bitbucket
search github/ bitbucket how to do it 🙂
Add new Jenkins Job
- in begining I mentioned that home folder is not writeable, so we are encountering several problems, like ssh can’t write into .ssh , maven can’t write into .m2 folder and so on. The only solution is to point all applications into writeable folder which is $OPENSHIFT_DATA_DIR
- Because of the problem above, you can’t use standard maven jobs but you have to use “Build a free-style software project”
- Source Code Management: git: your git url (i.e. git@bitbucket.org:majecek/testtest.git)
- Build: (add Execute shell): enter:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cd $OPENSHIFT_DATA_DIR | |
echo -e "<settings><localRepository>$OPENSHIFT_DATA_DIR/.m2</localRepository></settings>" > settings.xml | |
cd $WORKSPACE | |
mvn clean compile test package -s $OPENSHIFT_DATA_DIR/settings.xml |
- this creates setings.xml file and when runing maven commands – you have to specify where is the settings file
- check this site for more info
- next step is to add hooks in github/bitbucket – so after push in repo they will trigger jenkins to create new build – again check it in github/bitbucke or this site
Feed Sonar with data from Jenkins
This was quite a problem. I have to admit that I didn’t finish it, but found solution. Here is another problem, sonar and specially it’s mysql runs on different gear and openshift by default don’t allow any connection between gears nor from outside.
- install Sonar plugin into jenkins, add URL & jdbc url and all info needed
- I had to add into Sonar Aditional properties: -DSONAR_USER_HOME=$OPENSHIFT_DATA_DIR
- this is again, because sonar can’t write into home directory, so you have to point to writeable folder
Now you will face problem, that jenkins can’t connect to MYSQL DB – as said above, this is because gears can’t communicate to each other. There are 2 solutions:
- set up SONAR as scaled application – scalled applications can communicate to each other
- setup ssh port forwarding between applications
You can read more here.
SonarQube part #2 – let’s feed it with some data
Posted: December 7, 2013 Filed under: java, Linux, Mac, programing | Tags: maven, sonar, SonarQube, SonarQube Runner Leave a commentIn previous article, I have showed you how to build sonarqube 4.0 on openshift , but let’s feed it with some data.
- Let’s create dummy j2ee project using maven
-
mvn archetype:generate
- cd <<project_name>>
-
mvn clean compile
-
- openshift port forward to access database
-
rhc port-forward <<APPLICATION_NAME>>
- you should see something like this:
Service Local OpenShift
——- ————– —- —————
java 127.0.0.1:8080 => 127.X.X.X:8080
mysql 127.0.0.1:3306 => 127.X.X.X:3306 - database can be accessed on localhost:3306
-
Now we have few options how to feed sonar
- maven – best for maven projects
- sonarqube runner – best for java legacy code
- jenkins,….
Maven projects
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | |
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> | |
<modelVersion>4.0.0</modelVersion> | |
<groupId>eu.chowaniok</groupId> | |
<artifactId>j2eeApplication</artifactId> | |
<version>1.0-SNAPSHOT</version> | |
<packaging>jar</packaging> | |
<name>j2eeApplication</name> | |
<url>http://maven.apache.org</url> | |
<properties> | |
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> | |
<sonar.language>java</sonar.language> | |
<sonar.host.url>http://127.0.0.1:8080</sonar.host.url> | |
<sonar.jdbc.url>jdbc:mysql://localhost:3306/APPLICATION_NAME?useUnicode=true&characterEncoding=utf8</sonar.jdbc.url> | |
<sonar.jdbc.username>mysql_username</sonar.jdbc.username> | |
<sonar.jdbc.password>mysql_password</sonar.jdbc.password> | |
</properties> | |
<dependencies> | |
<dependency> | |
<groupId>junit</groupId> | |
<artifactId>junit</artifactId> | |
<version>3.8.1</version> | |
<scope>test</scope> | |
</dependency> | |
</dependencies> | |
<build> | |
<pluginManagement> | |
<plugins> | |
<plugin> | |
<groupId>org.codehaus.mojo</groupId> | |
<artifactId>sonar-maven-plugin</artifactId> | |
<version>2.1</version> | |
</plugin> | |
</plugins> | |
</pluginManagement> | |
</build> | |
</project> |
5 things to change or consider:
- jdbc url – make sure you have correct url, port, application name
- mysql username
- mysql password
- sonar host url
- I am using maven version 3 – in case you have maven version 2 you have set different dependences
to run:
mvn clean compile sonar:sonar or (including profile name to be used) mvn clean compile sonar:sonar -Dsonar.profile="Sun checks"
SonarQube Runner
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sonar.projectKey=eu.chowaniok:j2eeApplication | |
sonar.projectName=j2eeApplication | |
sonar.projectVersion=1.0-SNAPSHOT | |
sonar.sources=src/main/java | |
sonar.language=java | |
sonar.sourceEncoding=UTF-8 | |
sonar.binaries=target | |
sonar.host.url=http://127.0.0.1:8080 | |
sonar.jdbc.url=jdbc:mysql://localhost:3306/APPLICATION_NAME?useUnicode=true&characterEncoding=utf8 | |
sonar.jdbc.username=mysql_username | |
sonar.jdbc.password=mysql_password |
4 things to change or consider:
- jdbc url – make sure you have correct url, port, application name
- mysql username
- mysql password
- sonar host url
to run:
- you have to download SonarQube runner & set PATH variable
export SONAR_RUNNER_HOME=/Path/to/SonnarRunner/sonar-runner-2.3 export PATH=$SONAR_RUNNER_HOME/bin:$PATH
- create file called “sonar-project.properties” and fill it with info mentioned above in gist
- run:
sonar-runner
Now change code (i.e. add empty private method, named with upper case letter, ….) and run analysis again to feed sonar. Check sonar – it shows you all violations and issues in your code, … (also it depends on plugins you have installed on your sonar)
Example project can be found on Bitbucket
How to run SonarQube 4.0 on openshift
Posted: December 6, 2013 Filed under: Linux, Mac, programing | Tags: git, openshift, redhat, sonar, SonarQube 4 CommentsI have managed to run latest SonarQube on openshift for free.
Because openshift has bug you can’t just have one-line command to do all setup for you, but I had to separate it into several commands and two git repos.
Bug
you can’t have .openshift folder in repo – so I have to have 2 git repos
- git repo with sonar without (.openshift folder)
- git repo with .openshift folder with start & stop commands
How to get SonarQube 4.0 running on openshift
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rhc create-app sonar diy-0.1 mysql-5.1 –from-code https://bitbucket.org/majecek/sonarqube-openshift.git | |
cd sonar | |
git remote add upstream -m master https://bitbucket.org/majecek/sonarqube-openshift_addons.git | |
git pull upstream master | |
git pull origin master | |
git push origin master |
Description
- when RedHat fixes the bug, you should be fine, just with line #1
- cd into project
- add another git repo which holds .openshift folder with start & stop commands
- get changes from repo above
- pull from origin repo – git was complaining when I didn’t do pull
- push into openshift
- wait several minutes until sonar gets running
Thanks
Big thanks goes to Rui Rodrigues(@rodriguesrmb) as he managed to solve port binding problems and update java wrapper with new version