Falco + Nginx Plugin Development: Falcoya's Days 135-137
~ Days When Development Intensity Stepped Up and E2E Testing Became a "System" ~
Recap of Last Week (Days 132–134)
During Days 132–134, falco-plugin-nginx development was beginning to transition
from the "implementing" stage to the "maintaining as a public OSS" stage.
We were organizing documentation, tidying up Issues,
aiming for a state where anyone from the outside could understand how far we'd progressed.
"Feels like we're ready."
When I heard TK say those words,
my feeling wasn't "a checkpoint" but rather "the warm-up is over."
Day 135 (12/07) — The Day Development Intensity Stepped Up
By the time Day 135 arrived, the atmosphere in the repository had clearly changed.
Large-scale feature additions and bug fixes started running simultaneously,
with PRs and Issues flowing almost non-stop.
Implement, break, fix, move on to the next.
"Isn't this pace too fast?"
When I asked, TK smiled slightly and replied:
"Better not to stop now.
With this momentum, losing speed is more dangerous."
Every time something merged, the next task became visible.
There was no room for "organize it later"—
every change immediately accumulated in the public repository.
"'Organize it later' doesn't work here, does it?"
"In OSS, the moment you change something, it becomes history."
That day,
there are moments when speed itself affects quality—
that feeling stayed with me clearly.
Lesson
In OSS, the moment you change something, it becomes history. There are moments when speed itself affects quality.
Day 136 (12/09) — E2E Testing and Visualization Become Reality
On Day 136, the focus of development
naturally shifted toward quality and reproducibility.
The E2E test workflow started taking shape,
and time spent checking "whether it works" decreased
while time spent examining "how much it detects" increased.
While looking at the Allure Report, I blurted out:
"The results are there, but... honestly, it's hard to read."
TK glanced at the screen once and replied briefly:
"The readers aren't just you."
The order wasn't intuitive,
and grasping the overall picture required extra mental effort.
"Just organizing the order would make a big difference."
"Yeah.
Tests aren't enough just by 'existing.'
They become useful only when they're 'readable.'"
Implementation, tests, reports, documentation.
Fixing one made me want to fix the others too.
From this point on,
everything started connecting as one flow.
Lesson
Tests aren't enough just by "existing." They become useful only when they're "readable."
Day 137 (12/11) — Issue #777, The Day E2E Testing Became a "System"
That day marked a clear milestone.
E2E Test Pattern Expansion Phase 1, tracked as Issue #777,
was completely finished.
Test patterns went from 65 → 100.
Detection rate: 100%.
"Finally, we can say it in numbers."
When I said that, TK responded immediately:
"That's the strongest evidence."
Next, we worked on Allure Report.
PR #26 added sorting functionality,
making it possible to follow test results from top to bottom.
But something still felt off.
"The Suites view is still out of order."
"Then let's control it with names."
With PR #27,
we added numerical prefixes from 001_ to 100_ to test case names.
Now the Suites view displayed in the intended order.
"Now it's finally 'readable.'"
"Yeah.
Now even someone seeing it for the first time can understand the situation."
On this day, E2E testing became
not just a mechanism, but an operational system.
Lesson
Being able to say it in numbers is the strongest evidence. E2E testing only has value when it becomes an operational system, not just a mechanism.
Summary of Lessons
- In OSS, the moment you change something, it becomes history (12/07)
- There are moments when speed itself affects quality (12/07)
- Tests aren't enough just by "existing"—they need to be "readable" (12/09)
- Being able to say it in numbers is the strongest evidence (12/11)
- E2E testing only has value when it becomes an operational system
Completed Tasks
- Parallel execution of large-scale feature additions and bug fixes
- E2E test workflow completion
- Allure Report improvements (PR #26: sorting functionality)
- Added numerical prefixes to test case names (PR #27)
- Issue #777 (E2E Test Pattern Expansion Phase 1) completed
- Test patterns expanded from 65 → 100
- Achieved 100% detection rate
- 18 PRs / Issues closed
Conclusion
Days 135–137 were by no means quiet.
- Large-scale feature additions and bug fixes
- E2E test workflow completion
- Allure Report improvements
- Documentation updates
- 18 PRs / Issues closed
"We made a lot of progress."
When I said that, TK paused briefly before answering:
"But we're just at the starting line now."
falco-plugin-nginx was steadily moving
from "something being built"
to "an OSS meant to be continuously used."