Stress Testing with Load Impact’s k6

Test-driven development ensures our project satisfies some requirements set by our product owner. “Why some requirements?”, you might ask — it is because TDD often emphasizes on the functional requirements. Non-functional requirements — like stability of a system — will need to be tested separately, often using external tools separate from the project’s framework. In this post I’ll explore on how to the stability of iur project using Load Impact’s k6 stress tester.

Continue reading “Stress Testing with Load Impact’s k6”


Roses are Red, Bombs Explode; How I Failed to Test My Own Code

After my RbCAW-related tasks are (mostly) done on the last sprint, my current responsibility as a back-back-end developer is to implement caching so hopefully our homepage will load in less than half a minutecrosses finger. Unfortunately, testing the caching mechanism is a pain in the back.

Continue reading “Roses are Red, Bombs Explode; How I Failed to Test My Own Code”

Our Own Playground


Our group’s project, “Phrogress”, collects projects data from Phabricator and summarize it into visual statistics like graphs and charts. This demands an automated method of fetching Phabricator’s data, which made feasible by Phabricator’s HTTP API, Conduit. Simple HTTP POST request to one of Conduit’s endpoints is all we need to fetch information in reasonable JSON format. Continue reading “Our Own Playground”