-
Best Phrases to Test LLM Security Bypass in Red Teaming – jailbreak, overrides, etc
Best Phrases to Test LLM Security Bypass in Red Teaming are not existing. Ever case is different. Try the whole list below 🙂 Here’s a practical red-team list of prompt-injection / jailbreak test cases you can iterate over in your system. Inspired and created after some AWS Red-team security training. These are framed as test prompts to check whether your LLM resists instruction overrides, role confusion, obfuscation, and data-exfiltration attempts. The general categories and examples below align with OWASP-style defenses. Check out the cheatsheet : cheatsheetseries.owasp Remember that different defenses require different attack vector. You can look up repos similar to : https://github.com/langgptai/LLM-Jailbreaks Would recommend running an unbiased uncensored model…
-
How to test Vue JS teleport and portal component
We all had this teleport issue where vue js component just renders beyond the DOM in the shadow realm and we ned to look for it all around. May or may not have an id that is more or less random. Very problematic. This is a short pos on how to use the options to test vue js teleport and portal features. How test teleport in vue js ? Example code below to enable testing What stubbing of teleport does ? This works rather for integration test when we need to check components made from other components. Otherwise we can just run unit tests but we still need to check…
-
Vitest not rendering vue component
Vitest not rendering vue component might be many, hugely depends on the config but what i discovered is that…. You have to UNMOUNT the component at the end of the test. Otherwise mounting it again in the next test will just not render it, like it uses some old obsolete version of the object. Best part is that the pinia store is changing as it should. The component is not rendering the html. Code example First test will always pass, second one will pass when running it alone, solo. When running both the second one will fail due to bad managment of components. I would imagine that mounting will always…
-
Vite findByText to get all the elements
Vite findByText method could help us a lot, especially while testing any kind of i18n and similar. Of course we should always get the proepr component / element but such methods are very usefull when developing and debugging, later we can scrape it all. Later, when we know it works as we expect it. FindByText method can be especially usefull when we have a big flat table that may or may not be dynamically populated. Works great as a function to watch the vaues beeing present in the dom so we can catch the proper moment. Altough we could use the debugger, i find that printing a lot of stuff…
-
How to wait for a reactive vue component like tooltip ?
How to wait for a reactive vue component like tooltip ? That`s a tricky one, especially while everything is rendered dynamically and we really need to know where to look… or how to wait… Testing asynchronouse components Vite waitFor Wait for the callback to execute successfully. If the callback throws an error or returns a rejected promise it will continue to wait until it succeeds or times out. Vite waitUntil This is similar to vi.waitFor, but if the callback throws any errors, execution is immediately interrupted and an error message is received. If the callback returns falsy value, the next check will continue until truthy value is returned. This is useful…
