DEV Community: abigail armijo

What I Learned Exploring AI-Generated 3D: A Hands-On Tour of Meshy, Tripo, and Three.js

abigail armijo — Tue, 26 May 2026 04:02:44 +0000

Hi! I will share my experience building a POC to generate 2D and 3D images for a friend's project.

One friend asked me to attend a meeting at his house to define the user story for a project he is planning. This was my first in-person meeting since COVID.

The general idea is that, during the registration process:

The user answers some predefined questions and generates a 2D Dragon image with a predefined branding style.
The image is generated with an AI image API creation (could be nano banana, GPT, or something else)
Generate a 3D version of your dragon with Tripo AI and get the GLB file needed for Three.js
Add some predefined animations on Threejs to the dragon.

The initial step was researching the available APIs and their pricing.

Image generation

First, I checked and tried to generate images. For images, you have different options. If you want to use them for free and compare the same prompt across different AI models, you can use this to compare them: https://arena.ai/image/side-by-side.

I experimented with my logo, which was created some years ago. To improve the style, I want to remove the background, but the images added white and gray boxes instead of the actual transparent PNG or move the incorrect puzzle piece.

You can add text to generate your image, or upload an image. These are my experiments with Gemini

From one of my photos I requested:

Remove the background
Change the color of my jacket to red
Add a smile because I am always serious in photos
Add a soccer stadium background
Change the image like a Panini World Cup sticker.

I also created a banner for my LinkedIn after some experiments trying to add the logo and all in place, without overlapping text or the image with the profile picture, and with the logo in the correct position.

Another interesting experiment was adding an infographic to explain accessibility testing.

Gemini also includes some songs and videos, here is the link from my LinkedIn

Continue my experiments with images, I explore now the music option. I requested to the previous image, change to use the Mexican soccer jersey, and requested some music related to the soccer world… | Abigail Armijo Hernández 🇺🇦🇮🇱🇵🇸🕊

Continue my experiments with images, I explore now the music option. I requested to the previous image, change to use the Mexican soccer jersey, and requested some music related to the soccer world cup

linkedin.com

So sometimes, although you describe the A pose as returning to the T pose and it overlaps the image, some tips add context, for example:

Add context/role: For example, you are a graphic designer with experience in designing new characters.
Small and specific tasks: Don't try to modify an image with all instructions at the same time. For my panini, it was on steps: remove background, change jacket color, add some smile, change background to World Cup, and add panini. Also, I shared the current image of the last Mexican jersey.
Add some quality criteria and a checklist

I got better results with GPT-Image-2

3D Images

I asked Claude to suggest some options for the 3D images. Another alternative to Tripo is Meshy.

Also, it's important to understand the key concepts to achieve better results with 3D images and animations. We're easier with a dragon than a person.

A-pose: is the standard initial posture in which most characters are modeled: standing, facing forward, with the arms extended downward forming roughly a 45° angle with the torso (hence the "A" shape). This position is not random: it makes it easier to place the internal skeleton later. It prevents the mesh from deforming oddly in delicate areas, such as the shoulders or armpits, as the character starts to move.
Mesh: is the visible surface of the model, a kind of "digital skin" made up of thousands of small polygons (usually triangles or squares) joined together by edges and vertices. The more polygons it has, the more detailed and smooth the character will look, but it will also be heavier to process.
Rigging consists of placing a virtual skeleton made of bones and joints inside the model. Although the viewer will never see it, this skeleton is what allows the character to be animated: when a bone is moved (for example, the arm bone), the mesh surrounding it deforms in response to that movement, just as human skin follows the real bone.

Both APIs are very similar in price: around 30/40 tokens per image, whether from text or image. The image is textureless, and you can call another API to generate the texture or rigging.

For animations, both include animations, but are more for people. I couldn't find a flying animation, but with Claude, I can create one after a few attempts.

You can download the models and export to Mixamo and other software like Blender or Unity to use in your games.

You can also send the model to 3D printing services.

Tripo

Payments for API and Web designers use different credits. I tested with me as a model and dancing, but you need pose A, or else your jacket looks like one piece.

I tried one dragon and a girl, and the animations were bad, but as a tester, I was curious.

If you set an A pose, you get better results, but my logo wasn't added correctly after using the auto rig.

I tried to export and import to Mixamo, I got an error while exporting. And with the other model, my arms were wrong.

For some images, the 3D model is incorrect, and most of the auto textures are metallic.

To get some images of only my face, I forgot to mention that I need jeans, and some images generated were without pants.

Also, sometimes it wasn't following the A pose and generated a T pose or multiple images inside the image.

The support is not user-friendly, and they can have a solution in 7 business days. You need to add your email and model ID. I requested more clarification about the issue with the image, but the answer was that only one person is required, and that the A pose is mandatory.

This was my best result with some animations is better on laptops than mobile:
https://studio.tripo3d.ai/3d-model/c449581f-5da7-4bf9-8be0-1d1c2b6f3e6b?invite_code=CTeDxH

Meshy

It's easier, and I think the rig option is better because you can set the parts needed for rigging. The credits are shared between the API and the web designer.

Here I tried me as some QA image

A car, but the change in the color of the car to matte instead of metallic wasn't clear.

I saw the manual rig I added myself as a Lego, but I couldn't remove the knees.

Lego animation

The import from Meshy to Mixamo went smoothly, with no errors.

I requested support to remove the knees for lego animations and was added to the list of features if it becomes more popular, with at least more friendly and faster answers without my username or model ID and I got the answer faster.

This is one example with meshy:
https://www.meshy.ai/s/EQNVGv

Mixamo

This is an Adobe product that lets you upload your models and add predefined animations. I like it because the animations are better than the AI.

This is the import auto rigger.

The animation is better because the model has a cape and was animated correctly.

Ninja dancing video

Claude POC demo

I created an experiment to build a Svelte app that generates images in 2D and 3D for the dragons and the ninja, related to my Abi's testing dojo, my website to practice testing.

I got some errors with the animations maybe threejs animations are not very common. I got some errors from the API and for meshy I need to prepare the image for the rigging because if you don't limit the image you end with a image with the Rigging API max limit. That is on their API documentation with API parameter you limit that faces.

When using input_task_id, models with more than 300,000 faces are not supported for rigging. Please use the Remesh API to reduce the face count before rigging.

The solution was add should_remesh: true and target_polycount: 150000 directly on the API request

const res = await fetch(${MESHY_BASE}/openapi/v1/image-to-3d, { method: 'POST', headers: headers(), body: JSON.stringify({ image_url: imageUrl, model_type: 'standard', should_texture: true, should_remesh: true, target_polycount: 150000 }) })

You can try for a limited time because I only bought few credits: https://ninja-generator-910246220092.us-central1.run.app/

One thing I noticed is that most of the examples of 2D and 3D images were of white people. And some ninjas have the cap with holes. There may be some bias about that.

Solution to Challenge 1 - Login with Different Users

abigail armijo — Sat, 16 May 2026 14:54:14 +0000

Challenge #1 is done — here's my solution to Practice Real-World Testing Scenarios for QA: Challenge #1 - Login with Different Users

I created the Abi's testing dojo, a website with some of the challenges that I had to handle localization:

A global trade web app where that I have to test to ensure it was correctly translated into Portuguese. I got an Excel with the translation in English and Portuguese.
An e-commerce site for different countries TThe DOM elements differed across countries, so instead of adding a lot of if/else or switch cases, I refactored using CSS locators in a JSON file for each country. So the test steps were the same, and with a parameter, you can test across different countries.

So the first challenge is to test login with different languages and varying levels of access; the user role determines the menu displayed.

I prefer creating API tests with Postman because it is easier and focused on APIs, but I have also worked on two projects with RestSharp. I think RestAssured for Java is a very popular option, so I included the example with RestAssured for .Net

API Testing

I tested these scenarios:

Login

Login with the admin user returns the admin menu.
Login with a normal user will return the menu for normal users.
Menu without user returns status code 401
Menu access with a user with access to a menu link returns HasAccess true
Menu access with a user without access to a menu link returns HasAccess false

Usually, the dates should be in UTC, so on login, I checked that the expiration date was within 24 hours, and I added some time as bandwidth.

Postman

I usually create a folder to test different scenarios for a feature, using this naming convention: API_Scenario_Expected_Result. Example: Login_withAdminUser_ReturnsAdminToken

I always add utility function that contains common validations across all tests. There is also a package library option

In one project, the JSON returned by the API changed significantly, but with the global function, I only needed to update the function, and the error message was different for each API.

On each API request, you can use the global functions as:

// 1. Test that the status code is 200
utils.StatusOk();

You can execute your tests on Postman with different options:

** Postman scheduled option** You can, for example, schedule daily tests and receive an email if they fail. I used this option in one project.

Export collection and environment to a Git repo with Newman.
Postman Cli with the collection and environment IDs. I used this with one project with Bamboo as CI/CD.

You can also create a CSV file so I can run the same test with different test data. For example, the login will be the same; you only need to change the default language, and each language and menu should be in a CSV file with the same name as your environment variables.

You can install the Postman Report on Azure Devops to get the results on your Azure DevOps CI/CD

Postman Newman report on Azure DevOps

.NET

For .NET, I decided to try a new testing framework TUnit

For security, you will never store passwords in code; instead, store them as secrets on your computer or in Azure Key Vault.

If you are using Azure DevOps and you have Visual Studio, you can associate your API tests with the manual Test Case

RestSharp

RestSharp is a popular package for making HTTP Requests, although it's not focused on testing like RestAssured. I've worked with RestSharp in 2 different projects.

I also created a TestBase with global functions that include the Auth Bearer token in all requests that require the user token.

I usually add each file with the API to test, for example, login + Test.cs (e.g., LoginTest.cs), which extends BasePage.

I created a wrapper to call the API. If new versions of RestSharp introduce a breaking change, you only need to update the ApiClient class.

RestAssured

RestAssured iis very popular for Java API testing and uses the Given/When/Then syntax.

 var response = Given()
            .ContentType("application/json")
            .Body(loginRequest)
        .When()
            .Post($"{AuthUrl}/api/Users/login")
        .Then()
            .StatusCode(200)
            .And().Body("$.AccessToken", Is.Not(Is.Null<object>()))
            .And().Body("$.TokenExpiration", Is.Not(Is.Null<object>()))
        .DeserializeTo<LoginResponse>();

UI Testing

For UI testing, you have different options. I've worked with

I tried some AI options that can generate code for manual tests. I added the link to the article. I tested with the first version, so I guess it now includes more options

To create tests, I usually follow the Page Object Model (POM) and components to add common functionality, for example, to grids, date pickers, and combos. With this combo, I've worked on UI migration from Telerik webforms to Component One, so I only need to change the Grid from Telerik to Component One, instead of changing some helper or more code.

I explained in a video How to design a web automation testing framework

For the different languages, I created a data folder with the text for each language.

I created a fixture to set the current language from the playwright projects.

// Each project runs the full test suite once in that language.
// The project name is matched by the locale fixture in fixtures/index.ts to load the correct data/xx-XX.json file.
// To add a new language: add a project here, add the mapping in fixtures/index.ts, and create data/xx-XX.json.
  projects: [
    { name: 'English', use: { ...devices['Desktop Chrome'] } },
    { name: 'Spanish', use: { ...devices['Desktop Chrome'] } },
    { name: 'German', use: { ...devices['Desktop Chrome'] } },
    { name: 'Japanese', use: { ...devices['Desktop Chrome'] } },
  ],

Fixture

// Fixtures are shared test dependencies that Playwright injects into every test automatically.
// Instead of repeating setup code in each test, you declare it once here and use it as a parameter.
// This file exports a custom `test` object that replaces the default one from @playwright/test.
import { test as base } from '@playwright/test';

// Maps the Playwright project name (defined in playwright.config.ts) to a BCP-47 locale code.
// The project name is used as the human-readable label in the HTML report.
const localeMap: Record<string, string> = {
    English:  'en-US',
    Spanish:  'es-MX',
    German:   'de-DE',
    Japanese: 'ja-JP',
};

type Fixtures = {
    locale: string;
};

export const test = base.extend<Fixtures>({
    locale: async ({}, use, testInfo) => {
        await use(localeMap[testInfo.project.name] ?? 'en-US');
    },
});

export { expect } from '@playwright/test';

For the website, I used Transloco which uses a similar approach to JSON.

I follow the same security best practices for using the .env file with user and password information, and I also created API helpers, for example, to read Excel, PDF, or API files.

Playwright includes a global setup where you can store the session for different users and reuse it for different tests.

async function globalSetup() {
    await fs.mkdir(authFolder, { recursive: true });

    const browser = await chromium.launch();
    const page = await browser.newPage();
    await page.goto(process.env.BASE_URL!);

    const loginApi = new LoginApi(page);

    let userLogin: Login = {
        Company: process.env.COMPANY!,
        UserName: process.env.NORMAL_USER!,
        Password: process.env.NORMAL_PASSWORD!,
        KeepSession: true,
        Code: 0,
    };
    await storeToken(page, await loginApi.login(userLogin));
    await saveAuthState(page, 'normal-user.json');

And to use, you only need to add the state

test.describe('Valid access to the page', () => {
    test.use({ storageState: '.auth/normal-user.json' });

I add tags in general by feature to execute tests by tag. You can also create tags like regression, security, smoke.

With an additional npm package, you can add a tag with the Test Case ID from Azure DevOps, and each time you execute the Azure DevOps pipeline, it will mark the test failed, passed, or skipped on Azure DevOps.

I published the results on GitHub Pages. I used this approach with one project, but they wanted to store the last week in separate folders, and on that project, I connected it to Allure Report.

I also included the screencast and actions annotations to include the description of the steps on the video

You can check my solution code TestingDojo Code

Thanks for following along with my take on Challenge #1! Testing is all about continuous learning, so don't hesitate to ask questions or share your feedback below. If this helped you in any way, feel free to share it with the community.

Practice Real-World Testing Scenarios for QA: Challenge 1 - Login with Different Users

abigail armijo — Wed, 25 Mar 2026 03:30:25 +0000

Welcome to Abi's testing dojo challenges.

I am thrilled to finally launch this series of testing challenges designed to help you learn and practice testing with real-world scenarios.

As QA professionals, we know that nothing replaces the experience of tackling real scenarios on actual applications. That's why I've built a website to serve as your training ground for API Testing, E2E Automation, performance testing, accessibility testing, and more. It contains a dashboard, grids, different users, and languages.

I'll be publishing a new QA Challenge. These aren't just "dummy" or standalone exercises. They are designed to simulate the complex workflows that you face when you are working as QA.

To keep the website available to everyone, it automatically resets all the info. It redeploys the basic data every Sunday at 00:00 UTC.

Website: https://abi-testing-dojo-demo.azurewebsites.net/
Security API (Scalar): https://abi-testing-dojo-auth-demo.azurewebsites.net
Data API (Swagger): https://abi-testing-dojo-ar-demo.azurewebsites.net

The website is an accounts receivable dashboard for different companies. One server can have one or more companies, and each company can have different users with different levels of access.

An admin user can register new servers, companies, and users.

A standard user can only see the dashboard, reports, and config parameters for the dashboard.

Challenge 1: Log in with different users

A login is about more than just a username and password. To test professional applications, you need to understand some main concepts:

Authentication: The system verifies who you are by checking your credentials and issuing an AccessToken.
Authorization: Once you are logged in, the system checks what you are allowed to do. and which companies you can access based on your role.
Internationalization (i18n): Testing that the application supports multiple languages (the language switcher at the top of the page).
Localization (l10n): Testing that the application is correctly translated for a specific region (switching to Spanish or Japanese).

In this challenge, we will automate both using an Admin account and a Standard User account.

The Scenarios to test

You need to verify the login functionality for two different user with different roles:

The Admin (John Doe)
User: jdoe
Password: Admin+123
Companies: Northwind, Contoso, or Adventure Works
The Standard User (Jane Doe)
User: janedoe
Password: User+123
Company: Northwind

The Dojo Challenge

API Challenge:

Perform a POST request to the login endpoint. Verify you receive a 200 OK and a valid AccessToken.
Perform a post with invalid user and password.

E2E Challenge:

Automate the UI flow (Company, User, Pass), click Login, and verify the redirection to the dashboard. The menu is different for an admin and a standard user.

Pro Tips for this Challenge

Role-Based Access: Users shouldn't be able to log into a company without access.
Wait for the Dashboard: The dashboard loads data from multiple APIs. Ensure your E2E test waits for the charts to appear before declaring victory!
Save that Token: You’ll need the AccessToken for future challenges. Keep it handy!
Internalization: Log in by selecting a different language. You can use the Google option to translate to your preferred language

You can use environment variables for the user and password because for security is better don't store passwords in the code

My Solution

I’ll be sharing my own implementation for this challenge on https://github.com/apis3445/TestingDojo.

Postman (API Collections)
C# / .NET (API Automation)
Playwright (E2E Masterclass)

If you complete this challenge, share your repository or a screenshot of your passing tests and tag it!

My AI-Powered Portfolio: Built with Antigravity, Svelte & Cloud Run

abigail armijo — Thu, 29 Jan 2026 03:05:52 +0000

This is a submission for the New Year, New You Portfolio Challenge Presented by Google AI

About Me

I'm a software developer who also enjoys automation testing.

I'm currently working as a QA Engineer, and I enjoy creating automation frameworks from scratch tailored to the specific needs of the project.

I published some public examples, videos, and articles to share my knowledge with the community.

My project for this year is to share a website to practice testing with real-world scenarios that I created as a POC for a client. I redesigned the website with Antigravity and included translations to English and German.

I created this portfolio to showcase my best projects, and I enjoyed the challenge of building it entirely with AI.

Portfolio

How I Built It

I created my portfolio with Antigravity. I used the planning option to create the portfolio and shared links to my LinkedIn, GitHub, GitBook, and Substack to Antigravity help me to create my about and the sections for my porftoflio. Although the initial plan suggested was to use React, I changed the plan to Svelte instead of React.

I added my logo on .png and asked Antigravity to add as the favicon.icon. I requested to download my profile picture from Substack (or any of the links I shared), to add to the portfolio.

Antigravity helped me a lot with the UI, I requested some changes to make it more accessible and user-friendly. It also helped me with the deployment, including setting up environment variables for the Gemini API key for the AI feature.

The AI feature uses the Gemini Flash model (free tier), so the answers are limited and could fail for the limits of free version.

Antigravity help me with the prompt and change the design to use json files on each sections to include the sections as context for the GoogleGenerativeAI.

For my testing practice website, Antigravity helped me redesign the site, fix bugs, add generate English and German translations, and validate some ideas for the challenges that I will post in the next weeks, for example to include japanese.

The concept originated from a previous role, where I proposed a modern alternative to traditional PDF CVs for sharing consultant bios with clients. This newly created template is fully reusable—you simply need to update the JSON files to customize the content for each section

What I'm Most Proud Of

I am proud that I created this website in just a few hours; checking the planning and making adjustments was very helpful.

I love learning new things, so I enjoyed creating a new website only with Antigravity, as well as deploying to Google Cloud, which was new to me. And I learned the Google API for the AI feature.

I liked the redesign that Antigravity did for my Angular website, "Abi's Testing Dojo." This helped me to release the new version of the website 2 weeks ago.

Thanks to the Google AI team for this challenge, the opportunity to learn new things, and for reviewing my portfolio.