CAMITK-testcomponents(1)

✨ CAMITK-testcomponents ✨

okay bestie, welcome to the camitk-testcomponents manual page, which is section 1 of the manual (iykyk 💅). this is the lil tool that tests your component extensions one at a time, and honestly? it's giving main character energy.

---

🎀 NAME 🎀

camitk-testcomponents — CamiTK Tests Components. that's it, that's the name, slay.

---

🦋 SYNOPSIS 🦋

camitk-testcomponents [OPTIONS]...

---

🌸 DESCRIPTION 🌸

so here's the tea, bestie. camitk-testcomponents is built using CamiTK 6.0. if you wanna know more, please visit <https://camitk.imag.fr> — it's right there, go look, no cap.

(c) Univ. Grenoble Alpes, CNRS, Grenoble INP - UGA, TIMC, France — yes, the copyright line, we respect it, we love it.

okay so what does this thing actually do. camitk-testcomponents aims at testing a component extension individually. there are two possible levels of test, and you get to pick your fighter:

• level 1 will create a CamiTK application, load the extension and then open the provided component file. it verifies that the extension can be loaded without error and that the managed file (of corresponding extension) can be opened without error. lowkey just a vibe check on the loading. ✅
• level 2 will do the same as level 1 plus save the component to a new file and then close the component. it verifies that saving the file and closing the file can be done without error. so it's level 1 but with extra steps, and those extra steps are iconic. ✅

💀 heads up: any exception thrown by CamiTK or other dependencies is caught and will result in a EXIT_FAILURE return code. so if something goes wrong, you get told, fr fr.

the targeted users are in R&D departments or laboratories. so if that's you, hiii, this page is for you 🫶

---

💖 OPTIONS 💖

• --help, -h — print usage information and exit. the classic "wait what does this do" button, and she always delivers ✨
• --component, -c component — the component extension to be tested. please provide the full path of the dynamic library. not a relative path, not a vibe, the FULL path, bestie 🙈
• --input, -i file — input component file to test the actions on. please provide the full path to the file. note that this file is not modified — she's just looking, not touching, respectful queen 👑
• --level, -l level — the test level to proceed, either 1 or 2. and here's what they mean, one more time, because repetition is self-care:
  • 1 will create a CamiTK application, load the extension and then open the provided component file.
  • 2 will create a CamiTK application, load the extension, open the provided component file, save the component to a new file and then close the component.
• --output-dir, -o path — [Optional] directory where the output file will be saved. optional means you can skip her, but if level 2 is saving a file somewhere, you probably wanna know where it's going 🎀

---

👑 AUTHORS 👑

CamiTK and camitk-testcomponents is mainly developed by the Univ. Grenoble Alpes, CNRS, Grenoble INP - UGA in the TIMC UMR 5525 laboratory (CAMI team). shoutout to the CAMI team, they ate and left no crumbs 🔥

---

🌈 SEE ALSO 🌈

please visit <https://camitk.imag.fr> for more documentation on camitk-testcomponents. that's the whole SEE ALSO, short and sweet, periodt.

---

and that's the whole page, bestie 🦋 this was camitk-testcomponents 6.0, dated 2026-02-10, living in the CAMITK-testcomponents(1) manual — thanks for reading, go test your components, and don't forget your full paths 💜✨🎀