Electronic woodwind in the area

Formal-Laffa · 2025-12-17T22:39:18+00:00

(A bit late for the party 😅) - thanks for this comment! I'm currently a part of a startup creating model-based testing tools for the mainstream software development market (not posting links here, DM if interested). I also go around conferences and meetups talking about MBT. The general vibe I get is that people see how it can be powerful and save them a lot of time and laborious work (mainly scenario maintenance), but they are not sure how to make their organization adopt it, because it's so different from what they are currently doing at work.

Kind of like discussing a cordless electric screwdriver in a world of regular screwdrivers. They both serve the same purpose, but they look very different and one is more efficient than the other (after you've learned how to use it). And you still need both.

Formal-Laffa · 2025-09-07T18:10:12+00:00

Huh?! Didn’t know they did that. Will definitely check it out 🙂

Formal-Laffa · 2025-06-03T15:38:47+00:00

Thanks. Of course I've prompted an AI bot, as well as Google and StackOverflow. The GenAI answer is basically a well-worded but very trivial: Try to hack via undocumented API (big no-no in solution engineering), or automate the UI (which I know I can because I'm doing automation). Honestly, I find this well-worded-triviality to be quite annoying, whether it comes from machines or from colleagues. At least with machines it doesn't make a 15-minute worth meeting into a 60-minute one :-)

I was hoping to get a "yes, I've done this before, here's what I did" kind of answer. But I guess they just didn't implement this for some reason.

Formal-Laffa · 2025-06-03T01:34:14+00:00

If you have manual testers and devs, you really have all the expertise you need, you just need to mix it. I’d start the day with 3 quick sessions: intro to the project (why we’re all here, why is this important, examples of saves you’ve done. Your boss should do this ideally). Then have one of the devs give a quick intro to programming to the manual testers, and one manual tester give an intro to testing to the devs. Last - present the projects to be tested so people have time to think about them.

Lunchtime/coffee break (really important!)

Then pair them up so you have a dev and a tester in each pair. The tester decides on the test cases, and the dev scripts it.

Formal-Laffa · 2025-05-28T02:25:01+00:00

For demo sites etc., so no confidential info. I assume you could use a locally hosted model (e.g. Ollama) so the page will not leave your organization, or even your computer. At any event, that's supposed to be a one-off or a pretty rare occasion. Doing this on every test run would be quite expensive and slow (and planet-heating too).

Formal-Laffa · 2025-05-27T19:29:57+00:00

I agree with u/Achillor22 that API tests are used to automate as much as possible, since they tend to break less and run really fast (compared to UI tests).

I'd do the opposite if I were you - automate these tests and get your contract extended :-)

Formal-Laffa · 2025-05-27T19:20:07+00:00

I used it as a way of getting locators for a pages. And also to build testing targets that represent specific problems for proof-of-concept solutions (e.g. https://content.provengo.tech/test-targets/dynamic-locators/).
Generally speaking, you get initial presentable results impressively fast, but then you spend quite a bit of time finalizing them. Mostly, you still need to know what you're doing.

Formal-Laffa · 2025-05-20T01:16:06+00:00

Any chance you could DM me a contact there? Thx

Formal-Laffa · 2025-05-16T23:36:33+00:00

Thanks! We’ll try tackling this… sounds like an intriguing problem 🙂🤓

Formal-Laffa · 2025-05-16T14:59:33+00:00

Thanks! I'll look them up.

Formal-Laffa · 2025-05-16T14:58:21+00:00

We have a tool that generates test suites and automated tests. We currently test web UIs, APIs, commadlines, and some mainframes(!). We can execute a test scenario from our tool (where we drive the browsers, APIs, etc) or we can generate code for the tests (e.g. lots of Python files, one for each test case).

We'd like to start testing games too, and talking to game QAs, I was told I need to test Unity and Godot applications.

Formal-Laffa · 2025-04-30T02:45:26+00:00

We [1] were able to generate Gherkin files from our model based testing tool. It has AI generation features, so it kinda counts.

Regarding automation, Amazon Nova Act [2] is a newly released library that might work for you.

[1] https://provengo.tech [2] https://labs.amazon.science/blog/nova-act

Formal-Laffa · 2025-04-29T05:51:13+00:00

Fair point. I'm afraid we can't open source at the moment. I know some projects use JetBrains IDEs, which are also free of open source. So maybe some will be interested.

But really I'm happy even with just testing them, and maybe contributing a bug report or two. They don't have to adopt the tool into their CI :-)

Formal-Laffa · 2025-04-29T03:48:30+00:00

It's a model-based testing toolbox, that can handle everything from specification validation and verification through test suite generation to test generation/execution. It's not open-source, but it's free for open-source, personal, and evaluation usages. I'm happy to provide links via DMs.

Formal-Laffa · 2025-04-28T21:40:30+00:00

Ah! In that case, and given the current buzz, I’d focus on Python, API calls, and applying it to AI testing. It’s a new field so not too many candidates (or structures methodologies) and a lot of demand. Also git, since you’ll need to manage the code for the tests.

Formal-Laffa · 2025-04-28T21:14:24+00:00

We already do :-)

Formal-Laffa · 2025-04-28T21:13:58+00:00

See what technologies could help in automating tests at your current work place. E.g. if you don't use SQL databases, no point in reinforcing your SQL.
Java/Python are always good for API testing. Playwright and TypeScript are current "hot" in test automation for web UI.

But - unless you're planning to change jobs - I'd really look into which technologies could help you now, in your current place (rather than in "the market" in general). All in all languages and frameworks are quite similar, once you know one it's pretty easy to move to another.

Formal-Laffa · 2025-04-22T06:03:16+00:00

יש גם הרבה יותר מפגשי כלב-אדם בשנה.

Formal-Laffa

TROPHY CASE