Web Summit cancelled a whole day because of a “storm”.
In London we call that a normal rainy day lol
This was my second Web Summit, in Lisbon.
The first was in 2018 and started with an interesting story. I booked an Airbnb with two women I’d never met.
One I knew from the QA community. The other replied to a tweet I posted about a spare ticket to Web Summit. Calculated risk lol
Both became friends. Later we all met up again in Spain, at one of their houses.
Also in 2018, a Microsoft “AI in action” Celebrity Match booth told me I look like Ingrid Michaelson.
I keep wondering whether AI would still think that lol
This year was completely different. It was all about the people. I didn’t get to watch a single talk. Then day 2 got cancelled, so the last day turned into the busiest one.
Usually it’s the quiet day. Not this year. I missed it anyway. I was flying back to London. But I was super happy to catch up with Petronio, Jan and Andrรฉ. Andrรฉ is the reason I was there. He invited me, and we’ve been friends since Draper University.
Did you go this year ? Which talk should I watch first ?
P.S. I keep wondering how many of those 2018 startups are still running.
Andreessen Horowitz ran a chart this week that I haven’t stopped thinking about.
Using Revelio Labs data, it shows that since January 2025, tech job postings have been asking for more years of experience and listing fewer preferred skills. Both movements are in the range of 5-10%. Small. But they move together, and they’ve held for over a year and a half.
The roles driving it are data work, systems work, and Java.
a16z’s interpretation is worth quoting in spirit: when you’re working on a new frontier, the skills you need haven’t been defined yet. So the thing you hire for is the ability to figure it out as you go.
I want to take that seriously rather than treat it as a slogan, because from where I sit it describes something concrete.
Nobody knows what “good” looks like yet
Most of my work is quality assurance and software auditing, a lot of it with startups building on AI-generated code. That last part matters.
A skills list is a bet that the problem is stable. “Knows Cypress.” “Five years of Selenium.” “Comfortable with Postman.” Those are useful when the shape of the work is known and the question is whether you can operate the machinery.
The shape of the work is not currently known.
When a team is generating large volumes of code from prompts, the old assumptions break in ways that don’t show up in a job description. Code review stops being a bottleneck you optimise and becomes the entire game. Test coverage numbers start lying to you, because a model will write tests that pass against its own misunderstanding of the requirement. Consistency across a codebase goes up while coherence goes down: everything looks like it was written by the same competent stranger, and no one on the team can tell you why a particular decision was made.
There is no certification for that yet. There will be. It doesn’t exist today.
What experience actually buys
I’d argue “experience” is the wrong word for what employers are reaching for. What they want is calibrated judgement, and years are just the cheapest available proxy for it.
In practice it shows up as a handful of unglamorous instincts:
Knowing what to worry about. A model can generate a thousand test cases. Deciding which twelve failures would actually cost the company money is a different act entirely, and it depends on understanding the business, not the framework.
Reading a spec and noticing what isn’t in it. The most expensive defects I’ve found were never bugs. They were requirements that everyone had interpreted slightly differently, and the code faithfully implemented one of those interpretations.
Being suspicious of things that look fine. AI-generated code has a particular quality: it is plausible. It reads well. It has sensible variable names and tidy structure. Plausible code that is subtly wrong is harder to catch than obviously bad code, and the only reliable defence I know is a reviewer who has been burned before.
Knowing when to stop testing. Under-testing ships defects. Over-testing burns a runway that a startup doesn’t have. Getting that boundary right is close to pure judgement.
None of these are skills in the sense a job posting means. They’re the residue of having done the work and got it wrong a few times.
The audit angle, and why the clock matters
There’s a second chart in that same a16z piece that deserves attention from anyone in security or assurance.
The share of vulnerabilities exploited on or before the day of disclosure has climbed sharply, and the window between a vulnerability being found and being exploited has collapsed to about a day at the median. The exploit survival curve, which a few years ago still had half of exploits usable after six weeks, now runs to zero at around six weeks.
Put those two charts next to each other.
Code is being produced faster than ever, by tools that are confident and fast and not accountable. And the time you have to catch a problem before someone else finds it is shrinking towards nothing.
That is an argument for verification as a first-class function, not a stage at the end of the pipeline. It’s also an argument for people who can look at a system and form a fast, decent hypothesis about where it’s weakest, because there increasingly isn’t time for the thorough version.
The part that bothers me
If the market is pricing experience over skills, the door for junior engineers gets narrower. That’s already visible in entry-level hiring numbers, and it isn’t a good outcome for anyone, including the companies doing the hiring, who will want senior engineers in five years.
I don’t think the answer is more credentials. A certificate is a skills claim, and skills are precisely what the market has started discounting.
The answer, as far as I can tell, is reps. Specifically, reps of a certain kind: real systems, real consequences, and someone experienced looking over your shoulder afterwards to tell you what you missed.
Experience is usually measured in years because years are easy to count. What actually accumulates is decisions made under uncertainty, followed by feedback. A junior engineer who has shipped, broken something, diagnosed it, and been reviewed properly forty times has more of the useful thing than someone who has held a title for six years and been carefully insulated from consequence.
That gap is compressible. Not to zero. But a lot of what gets called “you only learn this on the job” is really “nobody has bothered to teach this deliberately.”
One caveat
The shift in the data is 5-10%. That is real but modest, and a16z is careful about not overclaiming, so I will be too. Some of the change is aging-in-place and remote work widening the candidate pool, not AI.
And the piece makes a point I think is right: this is probably temporary. Once implementation matures, new skills get named, tooling standardises, and the skills-to-experience ratio swings back. The teams that will be defining those skills are the ones doing the work now and paying attention to what actually goes wrong.
Which is, in the end, another argument for being in the room while it’s messy.
It is 2a.m. and this is the only time I had to update the blog with the latest events !
I know the blog has been quiet since I opened my startup, and I wish I could be posting a lot more. I have been learning from left, right, center, inside and outside. This is the hardest thing I have done in my life, probably harder than moving to another country where I didn’t know anybody.
A few days ago, I had the opportunity to share a panel of Q&A with Simon Stewart at Novibet offices and also to speak at the Ministry of Testing Athens Meetup (MoT Athens ๐ฌ๐ท ) sharing the stage with Simon, Wim, Noemi and also Diego Molina (Uhul another South American here in Europe ๐ ).
The panel was really good, we arrived pretty much on brazilian time as we were really bad with directions ๐
Thanks gosh people were still motivated to ask questions when we arrived, and thanks Simon for taking the lead and presenting yourself first !
I know that we had around 200-300 guests like the last time I came to talk at MoT Athens and again people there makes completely the difference! Unique energy that I rarely see in other events where things are too corporative or full of egos (Not sorry for being honest ๐ )
My talk was a little different from the traditional testing presentation.
Instead of focusing on testing software, I explored a question that has been on my mind for quite some time:
What if we tested ourselves the same way we test software?
As testers, we question assumptions, look for edge cases, automate repetitive tasks, measure outcomes, and continuously improve. Yet many of us rarely apply the same rigorous mindset to our own lives, habits, careers, and personal growth.
During the session, I shared what I call the QA Mindset for Self-Growth, built around five principles:
Question everything.
Think in edge cases.
Automate the repeatable.
Measure what matters.
Iterate relentlessly.
What started as a framework inspired by software testing has become something I use daily as a founder. Building a company forces you to constantly challenge assumptions, identify risks before they become problems, create systems that scale, and continuously adapt based on feedback.
In many ways, entrepreneurship and quality assurance are surprisingly similar.
Both require you to become comfortable with uncertainty.
Both require you to look what you can control, yourself and take accountability not blaming others.
And both teach you that perfection is not the goal, the journey (continuous improvement) is.
The rest of the meetup was equally inspiring. We heard talks about AI-assisted testing, modern QA practices, security challenges, infrastructure vulnerabilities, and the evolving role of testers in a world increasingly influenced by AI. It was a reminder that our industry continues to move fast, and staying curious is becoming one of the most valuable skills we can develop.
I also loved seeing the community engagement throughout the event. From the interactive quizzes to the networking sessions and conversations between talks, it was clear that MoT Athens has built something special โฅ๏ธ
In the end the feedback was so positive – but you know me – I like the constructive feedback !
Screenshot
Thanks for Diego for pointing me out the things I can improve for the next and try to reduce my anxiety and my dry mouth and the eternity that looked like when I was finally able to drink water. Of course this wouldn’t be me if I didn’t do something to embarrass myself and I spilled water when I was finally drinking ๐
A huge thank you to the organizers, volunteers, speakers, and everyone who attended. Organizing events like these takes an enormous amount of effort, most of which happens behind the scenes.
Also thanks for Satoshi Nakamoto that was presented there (find him on the quiz picture) – unfortunately he was not the winner, so I couldn’t finally meet him lolz
Screenshot
And personally, thank you for welcoming me and giving me the opportunity to share ideas that sit at the intersection of technology, testing and personal development.
Moments like this remind me that growth rarely happens in isolation !
Hopefully, it won’t take me until 2a.m. again to write the next blog post.
This past week, I had the incredible opportunity to lead two workshops as part of Tech Women Week โ one virtual session streamed live on YouTube, and one in-person session hosted with Howard Kennedy LLP. Both were focused on one of my favorite topics: building your product with AI โ and honestly, I couldnโt have asked for a better experience even tho I have practiced only twice ๐
Thanks gosh I have been working with AI and products for a long time, so no need to practice at all. If you have missed both, this is the recording:
I was doing a research in the beginning to check what people have been using and also what stage they were in their journeys, really interesting how people still go first to chatgpt even to create the product… ๐ง
42% were in the POC (Proof of Concept) stage,
38% were still shaping the idea,
17% were working on their MVP,
and just a small number were in validation or product-market fit.
AI tools are evolving fast โ new ones every week, each promising to save time, boost productivity, or unlock creativity. My message during the workshop was simple: ๐ Donโt chase the trend. Start with your goal, then find the AI tool that fits that specific purpose.
Also, another take away important was AI is not flawless and you still need to review security, audit the code before you scale and publish sensitive data !! ๐จ Don’t follow blindly AI generated code.
Then the feedback was just amazing: I even had participants come up to me afterward saying, โThis was the best workshop Iโve ever been to.โ
No surprise I had really good feedback, but also things to improve, omg ALWAYS about the time ! I need to stop talking so much ๐
Some of my favourite feedbacks:
โI learned how straightforward it is to build โ I was always stuck in ideation, but now I can move forward.โ
โIt was very practical and actionable.โ
โEverything!โ
Some people wanted a longer session or a few more technical examples โ which, honestly, I love hearing because it means they were ready to go deeper. That tells me weโre building the right kind of momentum.
Seeing women confidently using AI to build, ideate, and ship their first products was everything I hoped for โฅ๏ธ
For the ones that were taking pictures with me after, please send them over, I am a not photo taker and the only picture I took was from the empty reception of the building when I was leaving the building ๐
Startup life is making me having less and less time for the blog and sharing my learnings, so pardon me ! Gonna put some updates from the past months here and share the side quests I done lately.
I had an ACL reconstruction surgery last week, got my knee ligament completely gone in one of the open mats before my first BJJ competition last year ๐ญ Unfortunately means no gym for at least 3 months, and being a bit dependent on my friend for a couple of days (which is a near death experience to me), but also it means I have a really good reason why I can’t get out of my cave ๐
In more exciting news, I’ve published 2 e-books to help with the coming events ! They are about using AI tools for building your product/MVP: VibeEbooks.co
The events will be during the Women in Tech Week, but you can come along regardless your gender:
Then, can’t remember exactly when was it, but I was also invited to join Blockdojo during the Angel Investment Awards 2025 and again met Emmie Faust from Female Founders Rise โฅ๏ธ
I promised myself this year I was not going to be a speaker in more than max 3 events, and I have been keeping up quiet good on this, so far I had only one in May and will have more 2 in October !
I have been trying to follow same pattern as Steve Jobs (Do at least 3 things that are important to achieve your next goal per day, the rest is noise). I have been delegating everything that I can (using ChatGpt Agent A LOT ๐ค) and don’t need my full attention, which gives me time to finally play a bit of Hogwarts Legacy and CS ๐
Robin woke up as soon as I started playing CS tho
Our first Hackathon was extremely better than what I was expecting. We had way more people signing up +100, some people dropped off (as expected) and then from this the founder was able to find not one, but TWO teams he wanted to work with ! Because of this now we are opening this new service for founders that want to have their MVP built during the hackathon or find their development team as consequence of it !
Last, but not least despite the ups and downs, and asking people to reply our survey….
We got a NPS Score of 10/10 from our last survey from the founders and 9/10 from the team ! That’s all for now !!
Again, late to post about this, maybe a month and a half ? ๐
The results of the SeedLegals Startup Awards were so surprising for me, I didn’t go expecting much, but while The Chaincademy didnโt take home a trophy this time, being named a Community Leaderfinalist and receiving an honourable mention is an achievement worth celebrating.
For a first awards appearance, itโs a strong signal of whatโs to come โค๏ธ โ and weโre just getting started !! Although I can’t disguise my disappointed face ๐
Eva Dobrzanska and the winners of the Community Leader Baltic Ventures !
And the winners of 2025 were:
๐ฅ Social Sensation:Wild ๐ค Community Leader:Baltic Ventures ๐ฑ Eco Innovator:UNDO ๐ Customer Champion:Wild ๐ธ Angel of the Year:Sutin Yang ๐ผ Top Workplace:Zinc ๐ฆ Soonicorn (Soon-to-be Unicorn):Fin Sustainable Logistics ๐ก Inspiring Entrepreneur:Dr Tom Pey โก Game Changer:Zetta Genomics ๐ Fund of the Year:Haatch ๐ Captivating Mission:WeWALK ๐ฅ Outstanding Achievement:Definely ๐ Startup of the Year:WineFi
Last month, I had the pleasure of hosting a workshop, “How to Get Your First Job in Tech: A Step-by-Step Guide,” remotely via ClassView Desktop. We connected with three ClassView Immersive Rooms, reaching 60 students from:
North Kent College, Dartford Campus
North Kent College, Tonbridge Campus
USP College, Seevic Campus
For 75 minutes, we explored the roadmap to breaking into the tech industry, and different paths and ways to find your path in tech! Specially nowadays with AI changing the space.
What We Covered
Hereโs a quick recap of what we dove into during the workshop:
Assessing Your Skills and Finding Your Path We talked about understanding your current skills, identifying gaps, and choosing the right tech career pathway tailored to your strengths and interests.
Crafting Standout Portfolios A big focus was on creating LinkedIn profiles, CVs, and GitHub portfolios that truly stand out to employers.
Supercharging Your Job Hunt I shared practical tips on accelerating your job searchโeverything from networking hacks to nailing interviews.
Validating Career Goals in Real-Time Students received actionable insights to align their career aspirations with their current skills and experiences.
AI Hackathon
One of my favorite parts of the session was seeing students quickly create some impressive portfolios in just four minutes with Lovable! Here are a few:
Huge congratulations to one of the students, who took home the top prize in our final quiz, earning a perfect score! Happy to see this is the moment where people are FULLY engaged, specially because there was a prize in the end ! ๐
My Takeaway
Being able to guide these students on their tech career journeys is always a rewarding experience. I received loads of great feedbacks from the students which is always comforting as I know dealing with teenagers is a BIG challenge ๐
And some pictures !
I canโt help but grapple with deeper questions about the future of our industry:
How can we help as a society to bridge the skills gap that is being widened by the speed of AI development?
The advancement of AI has the potential to exacerbate disparities in skills and opportunities. Are we equipping the next generation with the tools they need in this shifting landscape? Education, mentorship, and accessibility must be at the forefront of our collective effort to ensure no one is left behind.
If juniors and interns are being replaced by AI, are we heading towards a society without seniors?
This is a sobering thought. Without entry-level opportunities, how will we cultivate the experts of tomorrow? Experience is built incrementally, and AI canโt replace the nuanced understanding that comes from hands-on learning. As an industry, we must find ways to preserve pathways for growth while leveraging the capabilities of AI.
AI tools like Lovable.dev are changing app development, enabling rapid prototyping and giving the power to everybody to create functional applications through natural language prompts.
These tools are 20x faster to code than a developer, but they also introduce unique challenges in testing, debugging, and maintaining the generated applications. When you add AI to the team, you need to be vigilant.
Let’s explore below some challenges, and common scenarios that can happen and how you can test and identify them.
If you want to be able to use the code as a boilerplate and escalate the product after, don’t add 300 features before checking and testing it! AI creates hundreds lines of code making it harder and harder to review and maintain, test and check the code early as possible.
Also be aware, they will use whatever library they think is the best or they have partnership with. (Example: Lovable.dev will push you to use supabase) and some of these libraries/tools might not be the best/cheaper for your product (Check subscription prices). These AI tools might use libraries that are deprecated creating a conflict with other dependencies as you scale, introducing other bugs.
If you want to just test the market, prototype and you are completely okay to might have this MVP rewritten from the scratch then no need to worry about too much.
Common Challenges in Testing AI Coded Apps
1. Code Quality and Optimisation
Scenario: An e-commerce startup uses Lovable.dev to build a shopping platform. The generated code includes a product listing feature but contains redundant database queries that degrade performance.
Generated Code Example:
// Generated by AI
let products = [];
for (let productId of productIds) {
let product = db.query(`SELECT * FROM products WHERE id = ${productId}`);
products.push(product);
}
Issue: The code queries the database inside a loop, resulting in multiple queries for a single operation.
If you only had a happy test scenario you wouldn’t be able to catch this one, so in this case you will need to actively check the database and it’s performance.
2. Limited Customization and Flexibility
Scenario: A nonprofit organization creates an event management app. The appโs AI-generated code fails to include the functionality to calculate the carbon footprint of events.
Generated Code Example:
// Generated by AI
events.forEach(event => {
console.log(`Event: ${event.name}`);
});
Issue: The AI didnโt include a custom calculation for carbon emissions.
This is typical, sometimes AI only codes the front-end, some of the interactions between the components, and uses hardcoded the data, but it is unable to create the backend or logic behind if not explicitly asked for and send the formula. This can be catch in a simple happy test scenario with different inputs.
3. Debugging Complexity
Scenario: A small business generates a CRM app with an AI tool. The notification system malfunctions, sending duplicate notifications.
Generated Code Example:
// Generated by AI
reminders.forEach(reminder => {
if (reminder.date === today) {
sendNotification(reminder.userId, reminder.message);
sendNotification(reminder.userId, reminder.message);
}
});
Issue: Duplicate notification logic due to repeated function calls.
Sometimes even AI is able to pick up this one. You know when they suggest to refactor the code ? This one would be easy to catch when doing your happy path scenario, checking if you have received the notification only once.
4. Scalability Concerns
Scenario: A social media startup builds its platform. The AI-generated code fetches user data inefficiently during logins, causing delays as the user base grows.
Generated Code Example:
// Generated by AI
let userData = {};
userIds.forEach(userId => {
userData[userId] = db.query(`SELECT * FROM users WHERE id = ${userId}`);
});
Issue: The loop-based query structure slows down login times for large user bases.
This one could be identified later in the development cycle, unless you are doing performance tests early on. Probably will catch this only when you have a large database of users, easy to fix, but can be fixed before you have this headache.
5. Security Vulnerabilities
AI coding is great when the stakes arenโt too high
Scenario: A healthcare startup generates a patient portal app. The AI-generated code stores sensitive data without encryption.
Generated Code Example:
// Generated by AI
db.insert(`INSERT INTO patients (name, dob, medicalRecord) VALUES ('${name}', '${dob}', '${medicalRecord}')`);
Issue: Plain text storage of sensitive information.
Another typical one for AI coded generated apps, usually they lack on security of the data. Be extra cautious when checking the data transactions and how the data is being managed and stored.
6. Over-Reliance on AI
Scenario: A freelance entrepreneur creates a budgeting app. When a bug arises in the expense tracker, the entrepreneur struggles to debug it due to limited coding knowledge.
Generated Code Example:
// Generated by AI
let expenses = [];
expenseItems.forEach(item => {
expenses.push(item.amount);
});
let total = expenses.reduce((sum, amount) => sum + amount, 0) * discount;
Issue: Misapplied logic causes an incorrect total calculation.
Another one that AI can catch while developing the app, because AI mix back and front end code sometimes is hard to debug even when you are a experienced developer, for someone that doesn’t have coding skills, then the challenge can be a bit more complex. AI can also help you to find the error, and you can catch this one probably not only when deploying, but also when doing your happy path scenario.
Not all AI coding platforms create tests on their own code unless explicitly asked for. Loveable for example don’t create any tests for their code. This is another thing you need to keep in mind when using these tools.
Another point is AI is not really good to keep up to date with all latest technologies, for example: All Blockchains, still not possible to do much, but a matter of time maybe ? These technologies keep changing and evolving every second you breath, AI can’t keep up yet, and humans can’t as well ๐
As you probably know I am a big advocate of emerging techs and I love to try new things. I am also lazy and I like to be as much efficient and productive with my time as possible ๐
Also, maybe because I saw the business of my father collapsing as he was not getting up to date with new technologies. Both my mom and my dad were COBOL developers.
My mom later had to become a teacher in Tech and my dad after opening his software development and education business had to close it. Both of my parents were one of the first ones to use and have PCs in my hometown, Santos.
Advanced code generation, Multi-language support, IDE integration
All developer levels
– Known to produce incorrect or insecure code in some scenarios. – Requires human oversight to validate outputs. – Subscription costs may be prohibitive for some users.
Complex debugging scenarios and large-scale refactoring
– Requires expertise to effectively guide and validate AI suggestions, especially in backend development – Continuous review necessary to maintain code standards
Multi-language support, AI chat function, Code explanation
Individual developers
– Struggles with domain-specific requirements and complex workflows. – Free tier lacks advanced features required by teams or enterprises.
Features and Considerations
Lovable.dev
Offers quick prototyping and MVP validation capabilities
Integrates with Supabase for backend and database features
Provides easy publishing and sharing options โค๏ธ
Replit
Includes AI-powered tools like Agent and Assistant
Offers a complete development environment with real-time collaboration
Suitable for educational purposes and quick experimentation
Bolt.new
Supports popular frameworks like Astro, Vite, Next.js, and more
Allows manual code editing after AI generation
Simplifies deployment with Netlify integration
AWS PartyRock
Designed for no-code AI app development
Leverages Amazon Bedrock for access to various foundation models
Cost-effective solution for small businesses to experiment with AI โค๏ธ
GitHub Copilot
Deep integration with the GitHub ecosystem
Powered by advanced language models (GPT-4o and Claude 3.5 Sonnet)
Offers built-in security scanning and best practices recommendations โค๏ธ
Qodo
Specializes in full-stack development support
Provides advanced context understanding across multiple files
Offers integrated testing and documentation generation
Codeium
Supports over 70 programming languages
Provides context-aware code suggestions
Offers a free tier with many excellent features for individual developers
A0.dev
Ideal for quickly generating React Native apps or UI components from basic descriptions
The Component Generator allows for the fast creation of individual UI components or screens.
The generated React Native projects can be extended and integrated with other tools, APIs, or libraries.
Cursor
Smaller coding tasks and projects
Teams seeking strong collaboration feature
Rapid prototyping and initial code generation
Cline
Integration testing and system-level operations
Developers who need flexible context management and model switching
Front-end tasks and design challenges
Projects requiring runtime debugging and end-to-end testing capabilities
What Developers think about it ?
Code Quality Concerns: The generated code not always adhere to best practices, be maintainable, or scale well.
Example: Seasoned developers might spend more time refactoring than coding from scratch.
Lack of Customization: AI tools may not fully capture complex or unique requirements, requiring additional effort to adjust.
Over-Reliance Risks: Relying heavily on AI can create dependency issues, making developers less adept at solving problems manually.
Privacy and Intellectual Property: Concerns about the security and data uploaded to these tools.
Overall, devs generally see AI coding tools as valuable for speeding up development and prototyping, which is also my opinion.
I have been exploring and using AI coding tools heavily and I can only recommend, this avoids you to spend money and time building something that you can easily test before you scale into a product.
The devs also emphasise that these tools are best used as assistants rather than replacements, requiring careful oversight and customisation to ensure high-quality and maintainable code.
Youโve just refactored your Terraform module to add the auto-scaling magic. You merge. You deploy. You go to bed. The next morning? Production is literally on fire ๐ฅ because your โtinyโ change accidentally nuked the database.
How to stop โOopsโ from becoming โOH NOโ …
Test-Driven Chaos Prevention ๐งช
Terraform tests (available in v1.6+) let you validate config changes before they touch your infrastructure. Think of them as your codeโs personal bouncer, checking IDs at the door.
Translation: โIf the bucket name isnโt โmy-glittery-unicorn-bucket,โ error and abort.โ
How Terraform Tests Save You ๐ค
1๏ธโฃ command = plan: Simulate changes without touching real infra. โWhat ifโฆ?โ but for adults. 2๏ธโฃ Assertions: Like a clingy ex, theyโll text you 100x if somethingโs wrong. Example:
assert {
condition = output.bucket_name == "test-bucket"
error_message = "This is NOT the bucket youโre looking for. ๐"
}
3๏ธโฃ Variables & Overrides: Test edge cases without redeploying. Example: โWhat if someone sets bucket_prefix to ๐ฅ?โ
Some Tips !
Mock Providers (v1.7+): Fake it โtil you make it. Test AWS without paying AWS ๐
Expect Failure: Want to validate that a config should break? Use expect_failures. Example:
run "expect_chaos" {
variables { input = 1 } # Odd number โ should fail validation
expect_failures = [var.input]
}
Translation: โIf this doesnโt fail, Iโve lost faith in humanity.โ (I have already tbh)
Modules in Tests: Reuse setup/teardown logic like a lazy genius. Example: A โtestโ module that pre-creates a VPC so you can focus on actual work.