Quality engineering & software studio — working worldwideStudio za kvalitetu softvera — radimo svugdje u svijetu

Software gets tested here.
Then it gets built.
Ovdje se softver testira.
A onda i gradi.

Creative Tech Lab is the studio of Marin Titlić — a quality engineer with four years inside regulated medical device software, now running test automation for clients and building his own products. Registered in Podgorica, working with teams anywhere.

Creative Tech Lab je studio Marina Titlića — inženjera kvalitete s četiri godine iskustva na reguliranom medicinskom softveru, koji radi test automatizaciju za klijente i gradi vlastite proizvode. Registriran u Podgorici, radi s timovima bilo gdje.

Book a test auditDogovori audit testiranja→
bench 01 — regression run 0000
0passedprošlo
0flakynestabilno
0.0swall timetrajanje

Illustrative output — not a live client runIlustrativni ispis — nije stvarno izvođenje kod klijenta

AvailabilityDostupnost Open for QA contracts (B2B)Otvoren za QA ugovore (B2B)
In the labU laboratoriju Four products in developmentČetiri proizvoda u izradi
BaseBaza Podgorica & Split — remote worldwidePodgorica i Split — remote, cijeli svijet
Local timeLokalno vrijeme —
Bay 01

Quality engineeringInženjering kvalitete

The main service. Test automation, API testing and QA process for software that has to hold up — including software that has to hold up in front of an auditor.

Glavna usluga. Test automatizacija, testiranje API-ja i QA proces za softver koji mora izdržati — uključujući softver koji mora izdržati i pred revizorom.

01 / UI automation

End-to-end test suitesEnd-to-end test suite

Playwright with TypeScript, Selenium with Python, Tricentis Tosca. Suites built to be maintained by your team, not just handed over.

Playwright (TypeScript), Selenium (Python), Tricentis Tosca. Suite se piše tako da ga vaš tim može održavati, ne samo preuzeti.

02 / API

REST & SOAP testingTestiranje REST i SOAP servisa

Contract, integration and regression coverage with Postman and SoapUI, wired into the pipeline so failures surface on the commit that caused them.

Ugovorno, integracijsko i regresijsko pokrivanje kroz Postman i SoapUI, spojeno na pipeline da se greška vidi na commitu koji ju je izazvao.

03 / Regulated

Medical device softwareSoftver za medicinske uređaje

IEC 62304 work: requirement traceability in Jama Connect, verification protocols, documented evidence that survives review.

Rad po IEC 62304: sljedivost zahtjeva u Jama Connectu, verifikacijski protokoli i dokumentacija koja prolazi reviziju.

04 / Process

Test strategy & CITest strategija i CI

Where to automate and where not to, what to run per commit versus nightly, and how a small team keeps it green. Azure DevOps, Jira, Git.

Što automatizirati, a što ne, što vrtjeti po commitu, a što noću, i kako mali tim to drži zelenim. Azure DevOps, Jira, Git.

EngagementsAngažmani

Three ways to startTri načina da se krene

Test auditAudit testiranja

~1 week~1 tjedan
  • A written read of what you have today and what it actually coversPisani pregled stanja i onoga što testovi stvarno pokrivaju
  • Gaps ranked by risk, not by how easy they are to fixRupe poredane po riziku, ne po tome koliko ih je lako zakrpati
  • A shortlist of what is worth automating — and what is notPopis onoga što se isplati automatizirati — i onoga što se ne isplati
  • A working proof-of-concept suite on your highest-value flowRadni proof-of-concept suite na vašem najvažnijem toku
Good whenDobro kad You have tests but nobody trusts them — or you have none and need to know where to spend first. Imate testove kojima nitko ne vjeruje — ili ih nemate i treba znati gdje prvo uložiti.

Automation sprintSprint automatizacije

4–8 weeks4–8 tjedana
  • An end-to-end suite in your stack, not a framework you have to learnEnd-to-end suite u vašem stacku, a ne framework koji tek treba naučiti
  • Wired into CI so a red build means somethingSpojeno na CI da crveni build stvarno nešto znači
  • Fixtures and page objects your developers can extend without askingFixturei i page objecti koje vaši developeri mogu proširiti bez pitanja
  • A runbook and a handover session, recordedRunbook i snimljena primopredaja
Good whenDobro kad Manual regression is eating the release cycle and the team has stopped shipping on Fridays. Ručna regresija jede release ciklus i tim je prestao objavljivati petkom.

Embedded QAQA u timu

MonthlyMjesečno
  • Test strategy owned by someone, in writing, kept currentTest strategija koju netko doista drži, napisana i ažurna
  • The suite stays green — flakes get fixed, not re-runSuite ostaje zelen — nestabilni testovi se popravljaju, ne ponovno pokreću
  • Testability reviewed at pull-request level, before it is expensiveTestabilnost se pregledava na razini pull requesta, dok je jeftino
  • Release sign-off with evidence attachedOdobrenje release-a s priloženim dokazima
Good whenDobro kad You need a QA function but not yet a QA hire. Treba vam QA funkcija, ali još ne i zaposlenik na tom mjestu.

Pricing: fixed scope or a day rate, agreed in writing after a first call. No number gets quoted before the scope is clear. Cijena: fiksni opseg ili dnevnica, dogovoreno u pisanom obliku nakon prvog poziva. Broj se ne izgovara prije nego je opseg jasan.

ISTQB CTFLTosca AS1Tosca AS2Tosca TDS1Tosca AE1IEC 62304PlaywrightTypeScriptSeleniumPythonPostmanSoapUIRESTSOAPAzure DevOpsJiraJama ConnectSQLGit
Bay 02

Products in developmentProizvodi u izradi

Small, sharp software for small businesses — mostly aimed at the Adriatic, none of it pretending to be an enterprise platform. Every stage below is the real one.

Mali, precizni softver za male tvrtke — uglavnom za Jadran, bez glume da je enterprise platforma. Svaka faza ispod je stvarna.

P-01

Rental OSRental OS

For apartment ownersZa iznajmljivače

Booking, calendar and guest handling for apartment owners in Montenegro — plus a digital guest guide that answers the questions hosts get asked forty times a season.

Rezervacije, kalendar i gosti za iznajmljivače u Crnoj Gori — plus digitalni vodič za goste koji odgovara na pitanja koja domaćin dobije četrdeset puta po sezoni.

P-02

Invoicing & e-invoiceFakturiranje i eRačun

For paušalisti & micro firmsZa paušaliste i male firme

Invoicing aimed straight at the January 2027 Fiskalizacija 2.0 and eRačun deadline in Croatia. Built so a paušalist can use it without an accountant on the phone.

Fakturiranje ciljano na rok Fiskalizacije 2.0 i eRačuna u siječnju 2027. Napravljeno da se koristi bez knjigovođe na telefonu.

P-03

Chatbot platformPlatforma za chatbotove

For service businessesZa uslužne firme

One assistant, trained on a business's own material, dropped into their site in an afternoon. A version is already answering for an accounting firm — and the one in the corner of this page is the same idea.

Jedan asistent, naučen na materijalima same firme, ubačen na njihovu stranicu u jedno popodne. Jedna verzija već odgovara za knjigovodstveni servis — a onaj u kutu ove stranice je ista ideja.

P-04

MedQA DocsMedQA Docs

For medtech teamsZa medtech timove

Test documentation tooling for medical device teams: protocols, traceability and evidence generated from the tests you already run, instead of typed twice.

Alat za test dokumentaciju u medtech timovima: protokoli, sljedivost i dokazi generirani iz testova koje ionako vrtiš, umjesto da se pišu dvaput.

Bay 03

WebsitesWeb stranice

Taken on selectively, a few a year, when the project fits. Built, deployed and then kept running — not handed over and forgotten.

Radi se selektivno, nekoliko godišnje, kad projekt odgovara. Izrada, deploy i održavanje — ne predaja i zaborav.

Bay 04

Regulated workRegulirani rad

Four years on medical device software under IEC 62304. The habits it leaves behind are the reason the ordinary projects come out better too.

Četiri godine na softveru za medicinske uređaje po normi IEC 62304. Navike koje iza toga ostanu razlog su zašto i obični projekti ispadnu bolji.

TraceabilitySljedivost

Requirement → test → resultZahtjev → test → rezultat

Every requirement is linked to the test that proves it and the run that executed it, maintained in Jama Connect. Nothing ships untraced, and nobody spends the week before an audit reconstructing history.

Svaki zahtjev vezan je na test koji ga dokazuje i na izvođenje koje ga je odradilo, održavano u Jama Connectu. Ništa ne ide van bez traga, i nitko ne provodi tjedan prije revizije rekonstruirajući povijest.

ProtocolsProtokoli

Written before they are runNapisani prije izvođenja

Verification protocols are reviewed and approved before execution, then run against a frozen build. Writing the expected result first is also the cheapest way to find out a requirement was ambiguous.

Verifikacijski protokoli pregledaju se i odobravaju prije izvođenja, pa se voze na zamrznutom buildu. Pisanje očekivanog rezultata unaprijed ujedno je najjeftiniji način da se otkrije da je zahtjev bio dvosmislen.

EvidenceDokazi

Records, not screenshots in a chatZapisi, a ne screenshotovi u chatu

Results are captured as records someone can follow a year later: which build, which environment, which data, who ran it. The same discipline makes an ordinary bug report actually reproducible.

Rezultati se bilježe kao zapisi koje netko može pratiti i godinu dana kasnije: koji build, koje okruženje, koji podaci, tko je izvodio. Ista disciplina čini i običnu prijavu buga stvarno ponovljivom.

DefectsGreške

Severity tied to risk, not to moodOzbiljnost vezana uz rizik, ne uz raspoloženje

A defect's classification comes from the risk analysis, not from who shouted loudest in triage. It is the difference between a backlog you can prioritise and a backlog you argue about.

Klasifikacija greške dolazi iz analize rizika, a ne od toga tko je najglasnije vikao na trijaži. To je razlika između backloga koji se može prioritizirati i backloga oko kojeg se raspravlja.

Most teams do not need all of this. But the habits it leaves behind — write the expected result before the fix, keep the trail, let risk decide what is urgent — make ordinary software better too.

Većini timova ovo sve ne treba. Ali navike koje iza toga ostanu — napiši očekivani rezultat prije popravka, čuvaj trag, pusti rizik da odluči što je hitno — čine i običan softver boljim.

Method

How a job runsKako ide posao

Four stages, in this order, on every engagement. The third is the one most studios skip.

Četiri faze, ovim redom, na svakom poslu. Treću većina studija preskoči.

01

ScopeOpseg

A call, then a written scope with a fixed price or a day rate. No proposal theatre.

Poziv, pa pisani opseg s fiksnom cijenom ili dnevnicom. Bez ponuda od trideset stranica.

02

BuildIzrada

Short cycles, something working to look at early, and a weekly note on what moved.

Kratki ciklusi, nešto što radi već rano, i tjedna poruka o tome što je pomaknuto.

03

TestTestiranje

The part most studios skip. Automated coverage, edge cases, and a report you can read.

Dio koji većina preskoči. Automatizirano pokrivanje, rubni slučajevi i izvještaj koji se da pročitati.

04

Ship & keepObjava i održavanje

Deploy, hand over the keys, stay on for maintenance if you want it.

Deploy, predaja ključeva, a održavanje ostaje na nama ako želite.

FAQ

Before you write inPrije nego se javite

We have no automated tests at all. Where does that even start?Nemamo nijedan automatizirani test. Gdje se tu uopće kreće?

With one flow, not with a framework. The audit picks the path that would hurt most if it broke, proves a suite can run it in your CI, and only then widens. A suite nobody trusts is worse than no suite, so the first goal is a green run that means something.

S jednim tokom, ne s frameworkom. Audit bira put koji bi najviše zabolio da pukne, dokaže da ga suite može odvrtjeti u vašem CI-ju, i tek onda se širi. Suite kojem nitko ne vjeruje gori je od nikakvog, pa je prvi cilj zeleni run koji nešto znači.

Do you only test, or do you build as well?Radite li samo testiranje ili i razvoj?

Both, but not equally. QA is the main service and the thing to hire this studio for. Products and websites are the other two bays — built here, tested here, and shipped with the same discipline.

Oboje, ali ne jednako. QA je glavna usluga i ono zbog čega se ovaj studio angažira. Proizvodi i web stranice su druga dva odjeljka — rade se ovdje, testiraju ovdje i objavljuju s istom disciplinom.

Can you work inside our tooling?Možete li raditi u našim alatima?

Usually, yes. Playwright with TypeScript, Selenium with Python, Tricentis Tosca, Postman and SoapUI on the test side; Azure DevOps, Jira, Git and Jama Connect around it. If your stack is something else, say so in the first message — most of this transfers, and the honest answer comes back quickly if it does not.

Uglavnom da. Playwright s TypeScriptom, Selenium s Pythonom, Tricentis Tosca, Postman i SoapUI na strani testiranja; Azure DevOps, Jira, Git i Jama Connect okolo. Ako je vaš stack nešto drugo, recite odmah u prvoj poruci — većina se prenosi, a ako se ne prenosi, iskren odgovor stiže brzo.

Is manual testing part of it?Ulazi li ručno testiranje u to?

Yes, where it pays. Exploratory sessions and first-pass verification of a new feature find things no script was written to look for. Automation is for regression — the work that has to happen the same way every time.

Da, tamo gdje se isplati. Eksploratorne sesije i prva provjera nove funkcionalnosti nađu ono što nijedna skripta nije ni tražila. Automatizacija je za regresiju — posao koji se mora odviti isto svaki put.

Time zone, contracts, NDAs?Vremenska zona, ugovori, NDA?

Central European Time, from Podgorica and Split, so European hours are straightforward and a US East Coast morning overlap works. Contracting is B2B through CREATIVETECHLAB DOO, Podgorica, on a written scope. NDA on request, signed before anything sensitive is shared.

Srednjoeuropsko vrijeme, iz Podgorice i Splita, pa su europski sati bez problema, a preklapanje s jutrom na američkoj istočnoj obali je izvedivo. Ugovara se B2B preko CREATIVETECHLAB DOO, Podgorica, na pisani opseg. NDA na zahtjev, potpisan prije nego išta osjetljivo ide van.

What language should I write in?Na kojem jeziku da pišem?

Croatian, English or Italian. The answer comes back the same day, in the language you wrote in.

Hrvatski, engleski ili talijanski. Odgovor stiže isti dan, na jeziku na kojem ste pisali.

Contact

Tell us what's breakingRecite što vam puca

A bug that keeps coming back, a release nobody trusts, a product idea sitting in a notes app. Write in English, Croatian or Italian — an answer comes the same day.

Bug koji se stalno vraća, release kojem nitko ne vjeruje, ideja za proizvod koja stoji u bilješkama. Pišite na hrvatskom, engleskom ili talijanskom — odgovor stiže isti dan.

info@creativetechlab.agency
EntitySubjektCREATIVETECHLAB DOO
SeatSjedištePodgorica, MontenegroCrna Gora
FoundedOsnovano15.06.2026.
Works withRadi sClients worldwideKlijentima diljem svijeta
LanguagesJeziciHR · EN (C1) · IT

Nothing is sent from this page. The form writes the message for you — then you copy it, or open it in your own mail app. Ništa se ne šalje s ove stranice. Forma samo složi poruku — nju kopirate ili otvorite u vlastitom mail programu.