This post is a brief introduction to Git and it's commands. Made specially for those who are just starting out with Git, GitHub and their carrer in IT.
Also for those who are just curious.
This post is a brief introduction to Git and it's commands. Made specially for those who are just starting out with Git, GitHub and their carrer in IT.
Also for those who are just curious.
To maintain an integrated and optimized workflow in our project, we use Playwright as our end-to-end testing framework.
Situation (S) Our team needed an efficient way to ensure that rapid code changes didn’t introduce unexpected bugs. Manual testing was time-consuming and prone to oversight—especially as multiple pull requests would arrive daily. We lacked a quick feedback loop to catch regressions before merging.
Task (T) We aimed to establish a robust continuous integration (CI) pipeline that automatically ran end-to-end (E2E) tests on every push or pull request. By doing so, we hoped to reduce production defects, speed up feedback to developers, and increase confidence in new features.
Action (A) We integrated Playwright into our project and linked it with GitHub Actions. This involved:
Result (R) By adding automated E2E tests and running them on GitHub Actions, we:
To ensure that test automation keeps up with the project's code updates and revisions, we integrate Playwright with Git. This integration enables:
Playwright stands out by offering support for:
It also provides benefits such as:
A useful tool for offline tinkering when away from your devices
At Remote Flags we were recently tasked to build an IoT platform to manage and interact with IOT devices. These IOT devices would run with Revolution Pi, which is based on Raspberry Pi.
We didn't have access to their hardware, neither physically nor logically through a network communication protocol.
To facilitate new feature development as well as doing end-to-end testing, we decided to build a simulator, to mirror the hardware behavior when receiving and sending messages.
This solution described in this post uses the Revolution Pi software, revpimodio2
, written in Python.
If you're following our blog posts chronologically, you'll see I've made a blunder in the past of trying to use AWS Elastic Beanstalk to support 2 Nodejs web apps in the same instance. (see here). This blog post aims at providing a simple alternative using another AWS compute service, Elastic Container Service (ECS).
Let's get into it!
At Remote Flags, I was in charge of setting up the infrastructure for a small service to facilitate demoing the main application to interested people.
As we're a small team, and budget is tight, I figured I would use a single "non-critical infrastructure" server; this would contain small tools that, if they went down, wouldn't impact the overall availability of our service.
{
"typescript": "~3.9.7",
"aws-cdk-lib": "2.10.0"
}