Quality is a top priority for our load testing tool. Today I wrote my first AngularJS directive unit test.
As we are currently working on marketing our load testing solution we don’t get much time left for coding. We identified some issues that could spoil user experience. It could make us loose some prospects.
So I took one day off backlinking / mailing / phoning / marketing to return to my beloved IDE. One day of coding in six weeks, it feels like holidays! I took the opportunity to improve our frontend SonarQube metrics.
Our load testing tool is a full SaaS solution. Building the GUI was a real challenge, we ended with AngularJS.
Our load testing platform, OctoPerf, has its frontend made using AngularJs. But it was not always the case, and this article describes the journey that led us to this choice.
Java was all I knew When I graduated in 2007, all I wanted was to perfect my Java skills. I spent years as a consultant in several companies, chowing down Struts or JSF, Ant and Maven. I also created personal projects to learn JBoss Seam or GWT.
Sitemaps lets crawlers easily index your web pages. Learn how to get a sitemap.xml file for MkDocs.
Here at OctoPerf we love static website generators. Even if our load testing tool is made completely dynamic by AngularJS, our website and blog are generated using Jekyll.
The OctoPerf documentation is created with MkDocs. This wonderful tool allowed us to concentrate on the documentation content as the markdown syntax is really easy to comprehend.
Moreover, the responsive themes let us integrate the documentation directly into our performance testing tool:
When building a startup, is it really required to write crappy code to quickly get a working product? We don’t think so.
OctoPerf has been built from the ground with one unique idea: writing code that’s pleasant to work with. Code quality is our number one priority. When you create your own startup, you quickly understand that the number one enemy are not your competitors: it is yourself!
When creating a startup you realize that your product:
must be released as quickly as possible on the market, needs as many features as possible to catch back the competitors, must be bug free to give your users the best possible experience.
Performance improvements are great. But, they inevitably come with trade-offs. Know them and you’ll be safe.
Everyone knows that having a website which is fast is better than slow. But, did you know that improving the speed of your web application almost always comes with a trade-off?
Like Antoine Lavoisier said Nothing is lost, nothing is created, everything is transformed. What happens when altering a web or mobile app to improve its performances?
How fast do you want to be? First of all, you should ask yourself this question.
How to host a static website with Jekyll on Amazon S3 and Cloudfront? Get the best performances from anywhere.
Our need is to create a fast website, in as less time as possible. Time is money, and when you launch a Startup, it is a very scarce resource.
Best possible response times from anywhere in our geographical market (Worldwide: USA, Europe and India). An already designed website template, we are not CSS gurus, and building it from scratch takes too much time. Easy to customize, it must match our graphic design with just a few modifications.
Dilemna choosing between open-source load testing solutions: JMeter, Gatling or building a virtual users injection engine from scratch.
When we started to think how to build OctoPerf, about one year ago, we had several options to create our stress testing platform:
Write our own HTTP engine from the ground, Use command line tools like Curl, Reuse an existing open-source HTTP engine, but which one? (Gatling Tool, JMeter, Grinder…) It took us several months to choose which one was the right option. When you are building a startup, the biggest constraint is obviously Time.