Last year, I started working in Tokyo for the first time as a programmer1. I soon left the company for several reasons and became an employee of another company based in Fukuoka, which is the fifth largest populated city in Japan. One reason2 for switching the company was that I was not allowed to use Emacs in the project. Taking into account my past work on Emacs packages, it was a nonsense that he sent me to the project where I was not allowed to use Emacs.
One of the issues in developing an Emacs Lisp package was configuring a test suite. You could set up a Travis CI for an Emacs Lisp project using Cask, but it was not very elegant. You had to specify dependencies both in the library header and the Cask file, which was redundant. Recently, a utility named EMake has been released. I developed a solution for running package lint before, but EMake can run package-lint, byte-compile, and ERT/buttercup tests and does not depend on Cask.