Combining AI Experiments to create ChangeAtlas
01 Sep 2026
In this moment:
Justin Holsgrove
I've recently combined some of my AI experiments into an open source project called ChangeAtlas - it's a combination of the system map globs from this moment and the release query overlay from this moment. With some added features: A more accessible map/ list view and the ability to export the current view as its own Obsidian vault.
It currently works with Azure DevOps but I hope that contributors will be willing to get it working for whatever platform they use (Jira etc and all the stuff I can't verify).
Simply put: ChangeAtlas turns a release's tracker query into a shaded map of your software system.
The big idea being a list from a query of changes tell you what was intended to go out. That doesn't tell you where the system actually changed, or what sits one dependency away from the change, or which components have quietly been in the blast radius of a release. I hope that by mapping it we can better decide where limited testing time should land and catch issues in areas that were not previously considered.
Anyway, there is a basic demo you can click about on here. If you would like to contribute and get it working for your setup or other set ups I am accepting pull requests and am open to cool ideas of stuff to add to it too.
I will probably write a full blog post at some point and add to the observatory but in the meantime the repo is here: ChangeAtlas. Let me know if it is helpful to you!
It currently works with Azure DevOps but I hope that contributors will be willing to get it working for whatever platform they use (Jira etc and all the stuff I can't verify).
Simply put: ChangeAtlas turns a release's tracker query into a shaded map of your software system.
The big idea being a list from a query of changes tell you what was intended to go out. That doesn't tell you where the system actually changed, or what sits one dependency away from the change, or which components have quietly been in the blast radius of a release. I hope that by mapping it we can better decide where limited testing time should land and catch issues in areas that were not previously considered.
Anyway, there is a basic demo you can click about on here. If you would like to contribute and get it working for your setup or other set ups I am accepting pull requests and am open to cool ideas of stuff to add to it too.
I will probably write a full blog post at some point and add to the observatory but in the meantime the repo is here: ChangeAtlas. Let me know if it is helpful to you!
Justin Holsgrove
Senior Test Engineer/ QA Manager
He/Him
🤖 Test automator, engineer and QA Manager
✒️ testtechie.co.uk -> testtechie9.wordpress.com
🙆♂️ jholsgrove.github.io
Open To
Meet at MoTaCon 2026
Sign in
to comment
With servers in >250 cities around the world, check your site for localization problems, broken GDPR banners, etc.
Explore MoT
What I learned about influence by becoming a stakeholder
Advanced prompting skills to turn AI into your trusted testing companion.
Into the MoTaverse is a podcast by Ministry of Testing, hosted by Rosie Sherry, exploring the people, insights, and systems shaping quality in modern software teams.