Alternatives
Products that do what New Version 1.9.7 released does
Versioning for RealTestData
- 1
- 2
- 3
- 4
- 5IB
I got sick of the old software development loop: Change code -> Run tests -> wait -> wait some more -> look at failures. I decided to build a tool that will enable you to: Change code -> look at failures. No wait time, no explicit test running. Under the hood: - Runs the whole test suite and collects code coverage per test. - For each auto file save, analyzes the changes on the tests. - Runs changed tests in the background. - Display results, the loop time from change to test results is approx 250ms. Instead of: code -> alt+tab -> arrow up -> rerun all the tests -> wait ... -> test results…
2022 · github.com
- 6SV
Hi HN, I've been waiting to post what I've been working on for a few weeks now:) Today we're launching LayerVault, which is a version control system made for designers. The URL is http://www.layervault.com LayerVault keeps track of what you're working on without adding extra steps to your process. The app runs in your toolbar and tracks changes you make to your files. Basically — each time you create or modify a file you’re working on, LayerVault saves a copy. You can then login, flip through its versions, and download a version from a few weeks ago. It's pretty neat — and we’ve built some…
2011
- 7SV
I've already posted yesterday, but I'd really love to get comments, any kind of questions, suggestions and help would be greatly appreciated as it's an Open Source project of mine (and was for others during my studies at the University of Konstanz 6 years ago). Since then I spent countless ours to bring forth the idea of a versioned storage system, especially well suited for analytical tasks for timd-varying data. Especially I'd love to discuss what documentation you need, which next steps are necessary (JSON, Cloud...), API additions or changes... I've updated the README quiet a bit, such…
2018
- 8NO
Hey HN, we're Evis and Nick and we're excited to be launching Neosync (https://www.github.com/nucleuscloud/neosync). Neosync is an open source platform that helps developers anonymize production data, generate synthetic data and sync it across their environments for better testing, debugging and developer experience. Most developers and teams have some version of a database seed script that creates some mock data for their local and stage databases. The problem is that production data is messy and it’s very difficult to replicate that with mock data. This causes two big…
2024 · github.com
- 9
- 10
- 11DT
I built DDL to Data after repeatedly pushing back on "just use production data and mask it" requests. Teams needed populated databases for testing, but pulling prod meant security reviews, PII scrubbing, and DevOps tickets. Hand-written seed scripts were the alternative slow, fragile, and out of sync the moment schemas changed. Paste your CREATE TABLE statements, get realistic test data back. It parses your schema, preserves foreign key relationships, and generates data that looks real, emails look like emails, timestamps are reasonable, uniqueness constraints are honored. No setup, no…
Jan 2026
- 12
- 13OS
Hey HN, we're Evis and Nick, we're excited to be launching Neosync on HN! Neosync is an open source data replication and anonymization project that helps developers create safe, anonymized test data and sync it across all environments for high-quality local, stage and CI testing. This is how it works: 1. You select a job type. Today we support data sync jobs (these sync data between two databases and run on a schedule you define) and a data generation job (this generates synthetic data from scratch and sends it to a destination). 2. Next you define your source database and a destination(s)…
2023 · github.com
- 14
- 15HD
Hi HN, My background is on datascience and I thought during the last few weeks on how to turn the data into commodity problem: Getting any meaningful out of data can be erroneous, time-consuming and includes repeatable processing work (and it is done over and over again). Im trying to mitigate this by harmonizing data, so it is ready for being consumed via an API or Spreadsheet. After a few iterations I ended up with this prototype that I wanted to share with you. Please notice, that this is an early prototype and not a finalized product yet. Im also delighted to know your opinions or…
2023
- 16LP
Hey! My name is Dima, I am from Ukraine and I am the co-founder of Lost Pixel! We built this tool to solve our problems at work and decided to open-source it so more people can build their custom visual regression testing pipelines! If you want to chat about the tool or visual regression testing in general I am super excited to meet like-minded people! Thanks a lot for checking out the product and I hope it will serve you well if you decide to try it out :D
2022 · github.com
- 17
- 18MS
Hey HN, I’m the author. I built Misata because existing tools (Faker, Mimesis) are great for random rows but terrible for relational or temporal integrity. I needed to generate data for a dashboard where "Timesheets" must happen after "Project Start Date," and I wanted to define these rules via natural language. How it works: LLM Layer: Uses Groq/Llama-3.3 to parse a "story" into a JSON schema constraint config. Simulation Layer: Uses Vectorized NumPy (no loops) to generate data. It builds a DAG of tables to ensure parent rows exist before child rows (referential integrity).…
Dec 2025 · github.com
- 19LG
Hi HN! This is Assaf, Matan, and Yshay from https://livecycle.io/ Livecycle enables dev teams to collaborate and comment in context, on top of any preview environment. Using Livecycle, developers get clear feedback earlier in the release cycle leading to higher-quality products, a faster release cadence, and fewer context switches and misunderstandings. Livecycle builds and pushes a dev-like environment for every branch in your repo (or, if you prefer, you can bring your own environments). Any containerized application will work, and support for multiple containers via…
2023 · livecycle.io
- 20SS
I'm developing a storage system for versioning data at the subfile level, especially well suited for SSDs due to its log-structured COW nature. It implements a novel versioning algorithm called sliding snapshot, a diff-algorithm which makes use of our stable record-identifiers and optionally hashes, another diff algorithm for importing similar XML-documents as a versioned resource as well as novel XPath axis to navigate not only in space, but also in time. Recently, I've implemented a higher level, asynchronous REST-API with Kotlin (Coroutines) and Vert.x in a seperate module. The system is…
2018
- 21OS
Hey HN, we're Evis and Nick from Neosync (https://www.github.com/nucleuscloud/neosync). Since we last introduced Neosync on HN 4 months ago, we’ve made a lot of progress and we’re excited to be launching several new features. As a reminder, Neosync is an open source platform that helps developers anonymize production data, generate synthetic data, subset it and sync it across their environments for better testing, debugging and developer experience. We do all of this while handling referential integrity. Whether you have primary keys, foreign keys, unique constraints,…
2024 · docs.neosync.dev
- 22DA
2020 · github.com
- 23AL
Raymond here from Butter.dev, an LLM response cache built as a chat-completions proxy. Today we're launching a key feature for the platform: the ability to generalize on dynamic, templated inputs. Caching at the HTTP request level has the obvious problem of generalizability. Nearly no request is identical, due to templated variables (like names) and metadata (like timestamps), so exact-match cache lookups rarely hit. We solve this at Butter by using LLMs to detect dynamic content in requests and derive their inter-relationships, allowing the cache entry to be stored as a template + variables…
Jan 2026 · blog.butter.dev
- 24FS
I wanted to test mobile apps in plain English instead of relying on brittle selectors like XPath or accessibility IDs. With a vision-based agent, that part actually works well. It can look at the screen, understand intent, and perform actions across Android and iOS. The bigger problem showed up around how tests are defined and maintained. When test flows are kept outside the codebase (written manually or generated from PRDs), they quickly go out of sync with the app. Keeping them updated becomes a lot of effort, and they lose reliability over time. I then tried generating tests directly from…
Apr 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →