<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>input-framework on Yacin Nadji, Ph.D.</title><link>https://yacin.nadji.us/tags/input-framework/</link><description>Recent content in input-framework on Yacin Nadji, Ph.D.</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 23 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://yacin.nadji.us/tags/input-framework/index.xml" rel="self" type="application/rss+xml"/><item><title>The Cure for Exceptional Zeek Package Testing (Part 3)</title><link>https://yacin.nadji.us/posts/2026/08/the-cure-for-exceptional-zeek-package-testing-part-3/</link><pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate><guid>https://yacin.nadji.us/posts/2026/08/the-cure-for-exceptional-zeek-package-testing-part-3/</guid><description>This article was originally posted on Zeek&amp;rsquo;s blog.
Introduction Back in Part 1 and Part 2, we presented our motivational package, ip-distance, how you can easily write unit tests in BTest, and how you can generate events—either by hand or through Zeek&amp;rsquo;s event tracing utility—to test your Zeek content. However, there&amp;rsquo;s another case I&amp;rsquo;d like to cover where you can use Zeek&amp;rsquo;s ability to read its own logs using the Input framework to exercise your package&amp;rsquo;s functionality.</description></item></channel></rss>