Skip to content

update 1.1 ‐ 1.2

Jump to bottom
alzzdev edited this page Jun 11, 2026 · 1 revision

AtDork v1.2 – Configuration Management & Automated Testing

Release date: June 2026
Update from: v1.1 → v1.2

This release marks a significant step toward production readiness.
It introduces a flexible YAML‑based configuration system and a comprehensive automated test suite covering all core and library modules.

New Feature: YAML Configuration (core/config.py)

AtDork now supports persistent configuration through a single file, atdork.yaml.
Command‑line arguments and environment variables continue to work as before, but you can now define your preferred defaults in one place.

How it works

  1. AtDork looks for atdork.yaml in the current working directory (a custom path can be supplied with --config).
  2. Values from the file override built‑in defaults.
  3. Environment variables (prefixed ATDORK_) override both the file and the defaults.
  4. CLI arguments still have the highest priority.

Example atdork.yaml 

max_results: 30
region: "uk-en"
safesearch: "off"
delay: 1.0
proxy_file: "proxies.txt"
format: "json"
output_dir: "./results"

With this file in place, a simple python main.py -q "site:gov filetype:pdf" automatically uses your saved settings – no more repetitive typing.

Automated Testing Suite (tests/)

A complete pytest‑based test suite has been added to ensure stability and simplify future development.

Test coverage

Module tested Test file
Search logic, retries, backend fallback, proxy rotation test_scanner.py
Proxy validation, rotation, cooldown, auto‑removal, statistics test_proxy_manager.py
URL validation, spam detection, strict filtering test_validator.py
Query file parsing, batch execution, failure handling test_batch_runner.py
YAML loading, environment variable overrides, type conversion test_config.py
Multi‑threaded execution with fallback test_multi_thread_runner.py
Output storage (TXT, JSON, CSV) test_storage.py

All tests use mocked network calls – they run offline and finish in seconds.

Running the tests

cd AtDork
pip install pytest      # if not already installed
pytest tests/ -v

Why this matters for professionals

  • Reproducibility – atdork.yaml lets you share a consistent setup across your team.
  • Safety – environment variables (like ATDORK_PROXY) keep secrets out of command histories.
  • Confidence – the test suite catches regressions before they reach your workflow.
  • CI/CD ready – drop pytest into your pipeline and catch issues on every commit.

Compatibility

  • All existing command‑line flags and environment variables remain unchanged.
  • The old interactive mode and batch processing work identically.
  • The new configuration file is entirely optional; if absent, AtDork behaves exactly as in v1.1.

Feedback

We welcome issues and pull requests on GitHub.
If you find this release helpful, consider leaving a ⭐ on the repository.

Clone this wiki locally