← Back

Behind the Scenes

See how this portfolio was built — from traditional QA frameworks at Newfold Digital to agentic AI-assisted development. Side-by-side comparisons, architecture diagrams, and workflow recordings.

Traditional vs Agentic: Side by Side

TaskTraditional (Newfold)Agentic (Current)
Write test for new featureManual Cucumber feature file + step definitions + page objects (~2-4h)AI generates from Acceptance Criteria → human reviews + adjusts (~20min)
CI/CD pipeline configJenkinsfile hand-coded with Groovy syntax, tested via trial-and-errorAgent proposes pipeline → human approves + adjusts parameters
Framework architectureResearched patterns, POC'd, coded layers over weeksKATA framework scaffolded in hours via skills, composable from day one
Test reportingCustom reporter code per project, HTML/XML output formatsKATA reporter + Allure out of the box, historical trends baked in
Git workflowManual branching, conflict resolution, PR managementgit-flow-master skill handles branching + commits + PRs autonomously

Architecture Evolution

Two pipelines — same engineer, expanded toolkit.

Architecture diagram comparing Traditional SDET and Agentic QA pipelines

2019-2023: Traditional SDET

  • Cucumber + TypeScript Page Object Model
  • Robot Framework + Python for API tests
  • Jenkins pipeline with manual stage config
  • Allure reports, Jira traceability
  • Manual Cucumber feature file authoring

2025+: Agentic QA

  • KATA framework with component-action-test layers
  • AI-driven test generation from AC Gherkin
  • GitHub Actions CI with multi-stage orchestration
  • Autonomous mode gate bypass for sprint workflows
  • Health tooling: asset integrity, staleness, consistency

Media Gallery

Screenshots, diagrams, and recordings showing the portfolio and workflows in action.

screenshots-homepage-hero

screenshots-behind-the-scenes

screenshots-coding-session

screenshots-blog-listing

screenshots-CI-workers

screenshots-cucumber-code-session

screenshots-projects-page

qa-DTS-smoke-funtionalities-video-check-PROD

qa-bk147-tc10-not-found

qa-DTS-smoke-allure-graphs

qa-DTS-smoke-leng-options-ES-categories-section

qa-jira-board

qa-allure-tests

qa-DTS-smoke-suite-details

qa-bk147-app-shell-with-sidebar

qa-allure-smoke-report

qa-bk147-multi-tab

qa-bunkasi-allure-failed-case-details

qa-DTS-smoke-allure-report

qa-DTS-smoke-suites-PROD

qa-DTS-smoke-graphs-PROD

bunkai-qa-engineering-bk147-tc10-not-found

bunkai-qa-engineering-bk147-app-shell-with-sidebar

bunkai-qa-engineering-bk147-multi-tab

bunkai-qa-engineering-thumbnail

bunkai-qa-engineering-.context-PBI-epics-EPIC-BK-7-project-module-hierarchy-stories-STORY-BK-8-tms-project-create-a-project-inside-a-workspace-bk52-scoping-test-project

bunkai-qa-engineering-docs-media-demo

unc-agentic-dev-reports-evidence-06-pdf-triggered

unc-agentic-dev-reports-evidence-05-sidebar-biblioteca

unc-agentic-dev-reports-evidence-01-course-landing

unc-agentic-dev-reports-evidence-03-tab-bar

unc-agentic-dev-reports-evidence-07-after-pdf-still-locked

unc-agentic-dev-reports-evidence-02-mod3-forced-click

unc-agentic-dev-reports-audit-course-269-section-4

unc-agentic-dev-reports-audit-course-269-section-3

unc-agentic-dev-reports-audit-course-269-section-1

unc-agentic-dev-reports-audit-course-269-section-2

unc-agentic-dev-reports-audit-course-269-section-0

unc-agentic-dev-docs-pitch-images-gemini-cli-official

unc-agentic-dev-docs-pitch-images-gemini-cli-terminal

This Portfolio — Built with Agentic Workflows

Everything you see on nelthor.com.ar was planned, built, reviewed, and deployed using the agentic-dev workflow. The process:

  1. Design spec defined via/project-foundation
  2. Content strategy via/product-management
  3. Landing page scaffolded via/project-bootstrap
  4. Each feature shipped via/sprint-development
  5. Quality gates via health tools +bun run health:check
  6. Autonomous mode enabled for faster iteration