---
title: "aviad rozenhek (@aviadr1) | Hashnode"
description: "aviad rozenhek (@aviadr1) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@aviadr1"
---

@aviadr1

# aviad rozenhek

@aviadr1 · Joined October 2023

### [Your CI is green. Did the required tests actually run?](https://gigaverse-engineering.hashnode.dev/your-ci-is-green-did-the-required-tests-actually-run?utm_source=hashnode&utm_medium=feed)

A green gate might hide skipped required tests. Compare planned work with actual job results using CI-esta and a concrete GitHub Actions example.

2 min read · [gigaverse-engineering.hashnode.dev](https://gigaverse-engineering.hashnode.dev/your-ci-is-green-did-the-required-tests-actually-run?utm_source=hashnode&utm_medium=feed)

[Oct 22](https://hashnode.com/posts/your-ci-is-green-did-the-required-tests-actually-run/6ada739446b9665bbff32efb)

### [An empty affected-test list might accidentally run your entire pytest suite](https://gigaverse-engineering.hashnode.dev/an-empty-affected-test-list-might-accidentally-run-your-entire-pytest-suite?utm_source=hashnode&utm_medium=feed)

An empty test list might run your entire suite. Handle none, scoped and full plans explicitly before starting pytest or application services.

2 min read · [gigaverse-engineering.hashnode.dev](https://gigaverse-engineering.hashnode.dev/an-empty-affected-test-list-might-accidentally-run-your-entire-pytest-suite?utm_source=hashnode&utm_medium=feed)

[Oct 22](https://hashnode.com/posts/an-empty-affected-test-list-might-accidentally-run-your-entire-pytest-suite/6ada72f546b9665bbff32cef)

### [Test recovery with a full page of broken jobs, then one healthy job](https://gigaverse-engineering.hashnode.dev/test-recovery-with-a-full-page-of-broken-jobs-then-one-healthy-job?utm_source=hashnode&utm_medium=feed)

A full page of failing jobs might starve healthy work. Use pytest-obligation to test progress, retained work and successful retries.

2 min read · [gigaverse-engineering.hashnode.dev](https://gigaverse-engineering.hashnode.dev/test-recovery-with-a-full-page-of-broken-jobs-then-one-healthy-job?utm_source=hashnode&utm_medium=feed)

[Oct 22](https://hashnode.com/posts/test-recovery-with-a-full-page-of-broken-jobs-then-one-healthy-job/6ada72b9f34b8ed726c51547)

### [Your Django transaction committed. The Celery task never got sent.](https://gigaverse-engineering.hashnode.dev/your-django-transaction-committed-the-celery-task-never-got-sent?utm_source=hashnode&utm_medium=feed)

You save a document, then queue its publication. The happy path is two lines: document.save() # The process might die here. Nothing has reached Celery yet. publish\_document.delay(document.pk) Moving

2 min read · [gigaverse-engineering.hashnode.dev](https://gigaverse-engineering.hashnode.dev/your-django-transaction-committed-the-celery-task-never-got-sent?utm_source=hashnode&utm_medium=feed)

[Oct 22](https://hashnode.com/posts/your-django-transaction-committed-the-celery-task-never-got-sent/6ada72730f21fdecc40c5b04)