jasmine VS JDK

Jasmine is a behavior-driven development framework for testing JavaScript code. It's known for its clean, straightforward syntax and does not rely on any other JavaScript frameworks or a Document Object Model (DOM). Jasmine is often praised for its simplicity and ease of use in both frontend and backend testing environments.

The test frameworks section provides an in-depth look at MochaJS, Jest, Jasmine, Puppeteer, Selenium, and Playwright. We review each framework's ease of use, community support, and overall robustness, supplemented with example unit tests.

Vitest makes it effortless to migrate from Jest. It supports the same Jasmine like API.

JavaScript Popular tools for testing: Mocha, Jasmine, Unit JS, Jest

Internet Explorer is not actively tested anymore due to Internet Explorer retiring on June 15, 2022 and jasmine v4 has dropped IE support https://github.com/jasmine/jasmine/blob/main/release_notes/4.0.0.md

To execute your tests, you can create test scripts using popular testing frameworks like Mocha, Jasmine, or Jest. These frameworks provide a structured way to organize and run your tests, report results, and handle assertions.

Testing frameworks like Jest, Mocha, and Jasmine are crucial for software development, ensuring code reliability and correctness. They offer features like test suites, test cases, assertions, and asynchronous testing support.

The test framework used does matter for naming, because in some frameworks you'd use different naming conventions (i.e. the fluent naming used with https://jasmine.github.io/)

Learn more about Jasmine and Karma

I felt out of the loop, thinking that Zero VM was some kind of new distro for OpenJDK but chasing <https://packages.debian.org/sid/openjdk-22-jre-zero#:~:text=...> to <https://sources.debian.org/src/openjdk-11/11.0.23%2B9-1/debi...> lead me to https://github.com/openjdk/jdk/tree/jdk-22-ga/src/hotspot/cp...

It seems that it's a specific CPU target for the Hotspot JIT for non-mainstream architectures (or for research purposes, as I saw mentioned once)

Completely gutted from the OpenJDK, last I checked. See here for the culprit PR: https://github.com/openjdk/jdk/pull/18688

> Yes, they're changing one aspect of signal handler use to work around this problem. They're not stopping the use of signal handlers in general. Hotspot continues to use signals for efficiency in general. See https://github.com/openjdk/jdk/blob/9059727df135dc90311bd476...

This whole thread is about SIGSEGV, and specifically their SIGSEGV handling. However, catching normal signals is not about efficiency.

Some of their exception handling is still odd: There is no reason for a program that receives SIGILL to ever attempt continuing. But others is fine, like catching SIGFPE to just forward an exception to the calling code.

(Sure, you could construct an argument to say that this is for efficiency if you considered the alternative to be implementing floating point in software so that all exceptions exist in user-space, but hardware floating point is the norm and such alternative would be wholly unreasonable.)

> The wonderful thing about choosing not to care about facts is having whatever opinions you want.

I appreciate the irony of you making such statement, proudly thinking that your opinion equals fact, and therefore any other opinion is not.

This discussion is nothing but subjective opinion vs. subjective opinion. Facts are (hopefully, as I can only speak for myself) inputs to both our opinions, but no opinion about "good" or "bad", "nasty" or not can ever be objective. Objective code quality does not exist.

I remember talking to Brendan about the PreserveFramePointer patch during my first months at Netflix in 2015. As of JDK 21, unfortunately it is no longer a general purpose solution for the JVM, because it prevents a fast path being taken for stack thawing for virtual threads: https://github.com/openjdk/jdk/blob/d32ce65781c1d7815a69ceac...