January 2025 - Pharo-users - lists.pharo.org

Pharo News of the Week 05/2025

by Marcus Denker

# Pharo News of the Week 05/2025 - [Video] Tp33 first pattern programming: https://www.youtube.com/watch?v=EwPuypfRQTg - [ANN] Google Summer of Code 2025: Call for Students https://gsoc.pharo.org If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 11 - Backport fix-SDL-default-renderer-by-platform to Pharo 11 #17696 https://github.com/pharo-project/pharo/pull/17696 # Pharo 12 - Backport correction evaluation of dynamic variables from the debugger #956 - Backport correction evaluation of dynamic variables from the debugger #956 https://github.com/pharo-spec/NewTools/pull/956 - Update version in #newTools for BaselineOfPharo for Pharo 12 to âv0.9.2â #17691 https://github.com/pharo-project/pharo/pull/17691 # Fixes - Do not restore ffi methods if they are not installed #17686 https://github.com/pharo-project/pharo/pull/17686 - Fix broken Pharo image #17712 https://github.com/pharo-project/pharo/pull/17712 - Bring back 'Fit all' menu item #17709 https://github.com/pharo-project/pharo/pull/17709 - Fixes: 17680 RB-Rename-class-from-in-text-editor-select-the-class-of-â¦ #17681 https://github.com/pharo-project/pharo/pull/17681 - 17677 pharo syntax tutorial testtest divide two by zero signals zero divide #17679 https://github.com/pharo-project/pharo/pull/17679 # Rules - Edited two rules to implement that #initializeWindow: has to call super and can't override preferredExtent #17695 https://github.com/pharo-project/pharo/pull/17695 - Refactoring Engine https://github.com/pharo-project/pharo/pull/17654 # Window Handling - Migrate about window to Spec #17708 https://github.com/pharo-project/pharo/pull/17708 - Cleaning window title #17711 https://github.com/pharo-project/pharo/pull/17711 # VM - Forward port 10.3.3 to pharo-12 branch #903 https://github.com/pharo-project/pharo-vm/pull/903 - Improve project structure #904 https://github.com/pharo-project/pharo-vm/pull/904 # Iceberg / Git - Cleaning Spec #1885 https://github.com/pharo-vcs/iceberg/pull/1885 - Removing dead code #1890 https://github.com/pharo-vcs/iceberg/pull/1890 - Fix IceTipCommitBrowser to have a cleaner initialization of the model #1888 https://github.com/pharo-vcs/iceberg/pull/1888 - Clean protocols #1886 https://github.com/pharo-vcs/iceberg/pull/1886 - Improve protocols #89 https://github.com/pharo-vcs/libgit2-pharo-bindings/pull/89 # Newtools - SpClosedWindowPresenter don't add itself in last closed window now #969 https://github.com/pharo-spec/NewTools/pull/969 - No glamorous icon names #968 https://github.com/pharo-spec/NewTools/pull/968 - No glamorous icon names #967 https://github.com/pharo-spec/NewTools/pull/967 - Cleaning title definition #966 https://github.com/pharo-spec/NewTools/pull/966 - Introduce a new About Pharo based on Spec instead of Morphic #965 https://github.com/pharo-spec/NewTools/pull/965 - Categorize an uncategorized method #964 https://github.com/pharo-spec/NewTools/pull/964 - Closed window is now independent and works with Announcements #963 https://github.com/pharo-spec/NewTools/pull/963 - Post cleaning fix2 #962 https://github.com/pharo-spec/NewTools/pull/962 - Post cleaning fixes #961 https://github.com/pharo-spec/NewTools/pull/961 - On the class side of course #960 https://github.com/pharo-spec/NewTools/pull/960 - Fixing the build I hope #959 https://github.com/pharo-spec/NewTools/pull/959 - Cleaning spec #957 https://github.com/pharo-spec/NewTools/pull/957 # Cleanup - Cleaning spec #1709 https://github.com/pharo-spec/Spec/pull/1709 - Cleaning title definition #1711 https://github.com/pharo-spec/Spec/pull/1711 - Cleaning SpMorphic: less duplication around centered #1712 https://github.com/pharo-spec/Spec/pull/1712 - Branch: automatebenchresult, Adding the timing to the benchmarks , aâ¦ #17622 https://github.com/pharo-project/pharo/pull/17622 - Cleanup compiler extensions. #17662 https://github.com/pharo-project/pharo/pull/17662 - AST-Core-Tests should not depend on Monticello #17665 https://github.com/pharo-project/pharo/pull/17665 - Branch: RedoingClosePresenter, Deleted everything so SpClosedWindowListPresenter can be independant #17676 https://github.com/pharo-project/pharo/pull/17676 - Move (OC)DoItVariable to the compiler #17678 https://github.com/pharo-project/pharo/pull/17678 - Cleaning Presenter #17683 https://github.com/pharo-project/pharo/pull/17683 - Post clean fix2 #17693 https://github.com/pharo-project/pharo/pull/17693 - Reintroducing test methods in a way that they are not counted as simiâ¦ #17694 https://github.com/pharo-project/pharo/pull/17694 - Reduce usage of protocol initialize-release #17701 https://github.com/pharo-project/pharo/pull/17701 - Cleanup refactorings #17700 https://github.com/pharo-project/pharo/pull/17700 - Depends on Roassal branch Pharo13 #17705 https://github.com/pharo-project/pharo/pull/17705 - Removed the undeclared for now. #17706 https://github.com/pharo-project/pharo/pull/17706 - Cleanup Tests #17710 https://github.com/pharo-project/pharo/pull/17710

Jan. 31, 2025

Re: "Book release: Application Building with Spec 2.0" â New blog post on all: objects all: theTime

by giorgio ferraris

hello!, Thank you for the answer, I ordered the book today, please note that it still seems that is written in French. happy smalltalking giorgio On Thu, Nov 7, 2024 at 1:23â¯PM Koen De Hondt < koen(a)all-objects-all-the-time.st> wrote: > Hi Giorgio, > > Thank you for reporting the issue. > > Yes, it is an error. We saw it a few days ago, but it has not been fixed > yet. > > Best regards, > Koen > > On 7 Nov 2024, at 12:27, giorgio ferraris <giorgio.ferraris(a)gmail.com> > wrote: > > hello, > > The Amazon site says that the language is French. Is that an error? > > thanks > > ciao > > giorgio > > <Screenshot 2024-11-07 at 12.25.47.png> > > On Thu, Nov 7, 2024 at 6:32â¯AM Koen De Hondt < > koen(a)all-objects-all-the-time.st> wrote: > >> Dear Pharo users and developers, >> >> It required an enormous effort to review, rewrite, and extend it, but I >> am happy to announce that it is finally here: the book on application >> building in Pharo with Spec 2.0. >> >> I wrote a blog post about it >> <https://all-objects-all-the-time.st/#/blog/posts/9>. Happy reading! >> >> Ciao, >> Koen >> > >

Jan. 30, 2025

Google Summer of Code 2025

by Sebastian Jordan

Hello people, We are applying for the GSoC (Google Sumer of Code) this year (again)! Info: https://summerofcode.withgoogle.com/ TLDR: It is an initiative from Google for student/beginner coders to contribute to open-source projects. There are Organizations that propose projects (like us), Google selects some of them, and then the people can read the proposals and apply for them. If they are selected and everything goes ok, Google pays to the student (for his/her work) and to the Organization (for mentoring them). To be selected, we need a good list of ideas/projects where outside people can contribute. We have these from the last year: https://gsoc.pharo.org/ideas. So, Iâm sending this to please ask you: 1. If there is any idea listed where you are supervisor (you can use the filter) -> Check if it is still valid 2. If there is no, you can think of one :) 3. Any change (update of one existing idea, delete or add one) must be done in this JSON: https://github.com/pharo-project/pharo-gsoc/blob/master/data/ideas.json You can: - Send directly a Pull Request with the changes to the repo (https://github.com/pharo-project/pharo-gsoc) ð - Or send us the updated JSON, and weâll push it ð Remember that the mentors of any idea have to be available for: - Response to the student applications - Supervise their work (probably some kind of interactions weekly) It is better to be 2, 3, or 4 mentors per idea so we can guarantee availability. The deadlines (https://developers.google.com/open-source/gsoc/timeline) are: * February 11 - to make the list of ideas * February 27 - Google lists the accepted Organizations * March 24 to April 8 - students apply to projects * June / July / August - CODING More info: https://developers.google.com/open-source/gsoc/resources/guide Thank you all! GSoC organizers from the Pharo Consortium

Jan. 29, 2025

UK Smalltalk User Group meeting: 2024 retrospective and what to expect in 2025 - 29 January 2025

by UK Smalltalk

For our first meeting of the year, we'll hold a retrospective on what has happened in the Smalltalk world in 2024, and discuss what we can expect in 2025. Join us to share what you learned, and what you are looking forward to! This will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/305378616/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

Jan. 28, 2025

Pharo News of the Week 04/2025

by Marcus Denker

# Pharo News of the Week 04/2025 - [ANN] New VM Release v10.3.3 https://www.pharo.org/news/2025-01-21-VM10-3-3.html - [Blog Post]: Subject in SUnit Tests https://all-objects-all-the-time.st/#/blog/posts/ - [Survey] please take a second to take the spotter survey: https://sondages.inria.fr/index.php/319877?lang=en If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 11 - Update version in #iceberg for BaselineOfPharo for Pharo 11 to âv2.2.3â #17644 https://github.com/pharo-project/pharo/pull/17644 # Pharo 12 - Update version in #newTools for BaselineOfPharo for Pharo 12 to âv0.9.1â #17666 https://github.com/pharo-project/pharo/pull/17666 - Update version in #spec for BaselineOfPharo for Pharo 12 to âv1.3.5â #17643 https://github.com/pharo-project/pharo/pull/17643 # Features - Update Fuel for Pharo 13 #17635 https://github.com/pharo-project/pharo/pull/17635 # Fixes - Fixed fall back code on new tenured primitives by jordanmontt Â· Pull Request #17617 Â· pharo-project/pharo https://github.com/pharo-project/pharo/pull/17617 - Calypso: Fix remove protocol when there is no method in the protocol #17628 https://github.com/pharo-project/pharo/pull/17628 - Branch: realunclosewindow, added all behaviors needed to use SpClosedWindowListPresebter #17629 https://github.com/pharo-project/pharo/pull/17629 - Update word navigation to handle different character groups #17630 https://github.com/pharo-project/pharo/pull/17630 - Fix timestamp parsing in SourceFileArray #17633 https://github.com/pharo-project/pharo/pull/17633 # VM - Remove old versions of libgit in new builds #902 https://github.com/pharo-project/pharo-vm/pull/902 # Compiler - Move OpalCompiler-UI tests to OpalCompiler-UI-Tests #17664 https://github.com/pharo-project/pharo/pull/17664 - Move OCBytecodeDecompilerExamplesTest to Flashback #17663 https://github.com/pharo-project/pharo/pull/17663 # Iceberg /Tonel /git - Port Hernan's snapshot browser to Iceberg #1875 https://github.com/pharo-vcs/iceberg/pull/1875 - Improve error messages #123 https://github.com/pharo-vcs/tonel/pull/123 # CI/Bootrap/Image load - Load roassal before NewTool https://github.com/pharo-project/pharo/pull/17650 - Remove double loading of welcome browser #17655 https://github.com/pharo-project/pharo/pull/17655 - Load Microdown before NewTools (Anyway NewTools will load it) #17652 https://github.com/pharo-project/pharo/pull/17652 # Newtools - Branch: Pharo13, renamed it to presenter and cleaned the class #941 https://github.com/pharo-spec/NewTools/pull/941 - Merge ColorPicker in NewTools #954 https://github.com/pharo-spec/NewTools/pull/954 - Fix Code Rewriter to take care of the context's application #953 https://github.com/pharo-spec/NewTools/pull/953 - Remove method with equivalent in traits #952 https://github.com/pharo-spec/NewTools/pull/952 - Integrate Welcome Browser into NewTools by jecisc Â· Pull Request #951 Â· pharo-spec/NewTools https://github.com/pharo-spec/NewTools/pull/951 - Branch: Making Playground Memorizing its Size #949 https://github.com/pharo-spec/NewTools/pull/949 - Branch: FixingLastInitialExtentForWindow #948 https://github.com/pharo-spec/NewTools/pull/948 - Branch: 946-StFinder-produces-DNU-on-browse, Fixes: #964 #947 https://github.com/pharo-spec/NewTools/pull/947 - Add drag&drop support to inspectors #945 https://github.com/pharo-spec/NewTools/pull/945 # Spec - Allow passwords in SpRequestDialog, Fixes #1705 #1706 https://github.com/pharo-spec/Spec/pull/1706 - fix: make Fuel serialization work with native collections #1704 https://github.com/pharo-spec/Spec/pull/1704 - P13: Introduce metadata and properties support in SpAbstractPresenterâ¦ #1701 https://github.com/pharo-spec/Spec/pull/1701 # Cleanup - Remove dead code #17632 https://github.com/pharo-project/pharo/pull/17632 - Moving ColorPicker extension to the extended class. #17637 https://github.com/pharo-project/pharo/pull/17637 - Remove the refresh because we should not have a dependency from Morphâ¦ #17638 https://github.com/pharo-project/pharo/pull/17638 - Branch: MakingDrTestMemorizingSize. #17649 https://github.com/pharo-project/pharo/pull/17649 - Remove Morphic MCSnapshotBrowser #17659 https://github.com/pharo-project/pharo/pull/17659 - Remove dead code #17658 https://github.com/pharo-project/pharo/pull/17658 - Doing a pass on ProfStef. #17653 https://github.com/pharo-project/pharo/pull/17653 # Website - Update Companies.md: new form links #82 https://github.com/pharo-project/pharo-website/pull/82

Jan. 27, 2025

Little poll to help us improving Spotter

by stephane ducasse

Hi Pharoers Weâre gathering feedback to improve the Spotter tool in Pharo. The survey is quick and focuses on your experience with it, if you could take a few minutes to share your thoughts it would be great. Here's the link: https://sondages.inria.fr/index.php/319877?lang=en Best regards, Santiago StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

Jan. 25, 2025

Pharo News of the Week 3/2025

by Marcus Denker

# Pharo News of the Week 3/2025 - [ANN] IWST 2024 proceedings is now online at https://ceur-ws.org/Vol-3893/ - [Video] Phausto at the Audio Programmer meetup https://lucretiomsp.github.io/musicwithpharo/2025/01/16/phaustoAudioProgram… If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 11 - Backport multibyte commit message fix to Pharo 11 #1877 https://github.com/pharo-vcs/iceberg/pull/1877 - Backport changes making #cascadeFor:initialExtent:world: for RealEstateAgent use integral positions when using the worldâs center to Pharo 11 #17604 https://github.com/pharo-project/pharo/pull/17604 # Pharo 12 - Backport changes making #recalculatePageWidths and #recalculatePageHeights on SpMorphicMillerAdapter set the coordinates and dimensions to integral numbers #1694 https://github.com/pharo-spec/Spec/pull/1694 - Backport fix making #loadVersionFromFileNamed: on MCRemoteFileBasedRepository always answer the version #17615 https://github.com/pharo-project/pharo/pull/17615 # Fixes - Pharo 13 - more Robust CompiledMethod inspection, #936 https://github.com/pharo-spec/NewTools/pull/936 - Fix #loadVersionFromFileNamed: on MCRemoteFileBasedRepository to always answer the version #17613 https://github.com/pharo-project/pharo/pull/17613 - Branch: 17625-Clean-window-menu, Fixes #17625 #17626 https://github.com/pharo-project/pharo/pull/17626 - 17597 the code formatter does not pretty print well ffi calls #17598 https://github.com/pharo-project/pharo/pull/17598 - Branch: Another FFI call variation not formattable + add customisatâ¦ #17601 https://github.com/pharo-project/pharo/pull/17601 - Trying to make sure that we get the correct method class once we set â¦ #17595 https://github.com/pharo-project/pharo/pull/17595 - fix(sorting): Make many tables in inspector extensions properly sortable #924 https://github.com/pharo-spec/NewTools/pull/924 # Features - Allow to load a package in another environment #17591 https://github.com/pharo-project/pharo/pull/17591 # Newtools - added WindowManager package to exploit new SpClosedWindowPresenter #940 https://github.com/pharo-spec/NewTools/pull/940 - Branch: removeUnusedPreferredExtent, Fixes # 935 #937 https://github.com/pharo-spec/NewTools/pull/937 - Branch: Pharo13, Removing preferredExtent instance variable of class and code #932 https://github.com/pharo-spec/NewTools/pull/932 # VM - Prepare release v10.3.3 #901 https://github.com/pharo-project/pharo-vm/pull/901 - Update build and dev VM and image to latest pharo 12 release #900 https://github.com/pharo-project/pharo-vm/pull/900 - force non-shallow checkout on CI #899 https://github.com/pharo-project/pharo-vm/pull/899 - Normalize variable #897 https://github.com/pharo-project/pharo-vm/pull/897 - Adding test to test Ephemerons in the Old Space #702 https://github.com/pharo-project/pharo-vm/pull/702 # Spec - Make #transferFor:from: on SpMorphicTreeTableDataSource delegate to the adapter #1679 https://github.com/pharo-spec/Spec/pull/1679 # iceberg (git) - Redo of PRâ¯#1873 #1880 https://github.com/pharo-vcs/iceberg/pull/1880 - Remove duplicated methods #1876 https://github.com/pharo-vcs/iceberg/pull/1876 - renamed all ice git hub classes from model to presenter ( not model anymore) #1874 https://github.com/pharo-vcs/iceberg/pull/1874 # Cleanup - Cleaningtest that there are no selectors remaining that are sent but not implemented #17612 https://github.com/pharo-project/pharo/pull/17612 - Move LocalProcessException and LocalRecursionStopper to debugger packages #17621 https://github.com/pharo-project/pharo/pull/17621 - Move DependentsArray from Kernel to System-Model #17620 https://github.com/pharo-project/pharo/pull/17620 - Clean TransferMorph #17619 https://github.com/pharo-project/pharo/pull/17619 - Remove dependencies to the AST #17616 https://github.com/pharo-project/pharo/pull/17616 - Remove some methods with equivalent in superclass in Calypso #17592 https://github.com/pharo-project/pharo/pull/17592 - Remove duplicated methods #939 https://github.com/pharo-spec/NewTools/pull/939 - One less reference to RBParser + does not uselessly reformat code. #934 https://github.com/pharo-spec/NewTools/pull/934 - Fix testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits #938 https://github.com/pharo-spec/NewTools/pull/938 - little post migration and all the tests are green #931 https://github.com/pharo-spec/NewTools/pull/931 - Remove duplicated methods #1699 https://github.com/pharo-spec/Spec/pull/1699 - Remove unused class variable recently introduced #1698 https://github.com/pharo-spec/Spec/pull/1698

Jan. 24, 2025

Re: "Subject in SUnit Tests" â New blog post on all: objects all: theTime

by Richard O'Keefe

This makes the assumption that there is, most of the time, a single, unique, object that the test is clearly about. I hasten to admit that my unit testing practice needs a lot to be desired. But it has not been my experience that there *is* any such object much of the time. For example, to test a method, I will sometimes create two equal objects, manipulate one of them in the old trusted way, manipulate the other in the new way, and then see if the objects are equal again. Which then is *the* subject? The answer is neither, because what the test is *about* is not an object, but a method. Or again, I open a stream to a new file, create a complex object, persist it on the stream, close the stream, open another stream reading from the file, reconstitute an object from it, and then check that the two objects are isomorphic. Which is *the* subject? Neither, because what I am testing is the encoding and decoding methods, not the objects. The key paragraph is this one: <quote> One could argue that there is not always a single object under test. In some situations that is correct, for instance when testing the interaction between objects. But in my experience, most unit tests have a single object under test. </quote> And it is *this* that we really need a blog post on. I am very ready to believe that you are a much better tester than I am. (That wouldn't be hard.) But *something* interesting is going on when I think in terms of testing classes and methods to the point where I find the idea of testing a particular object almost incomprehensible, yet you think this is the norm. I take some comfort from the fact that the Gherkin language in Cucumber (and why oh which has nobody bothered to write down a proper grammar, let alone even an informal semantics, for it? How am I supposed to know what is and what is not legal Gherkin?) goes out of its way to conceal the existence of subjects, should they exist, from test reviewers, and calls what a test is about a "feature". Here are two tests for the Quaternion class: testMultiplicationByScalarCommutes sampleExactScalars do: [:x | sampleExactQuaternions do: [:y | self assert: (x*y) = (y*x)]]. testMultiplicationOfPowersCommutes sampleExactQuaternions do: [:x | |y z| y := x squared. z := x cubed. self assert: (y*z) = (z*y)]. These two methods test important properties of the #* method. Here's another one, part of testing the test data.. testExactScalarsAreExactScalars sampleExactScalars do: [:each | self assert: each isScalar. self assert: each isExact]. This tests the *methods* #isScalar and #isExact, and indirectly the code that generates the test data. It's not about any particular object. Nor is it about *one* method. It's very hard to write a test case that tests only one method. In fact my own rather embarrassing experience is that when a test case of mine failed it quite often wasn't the method I thought I was testing that was wrong. Returning to the persistence example, it's not testing #saveOn: (object saveOn: byteStream) or #restore (byteStream restore). It's testing that the two methods are properly related. It would be wrong to call it #testSaveOn: and it would be wrong to call it #testRestore. There's a distinction here: it *is* possible to write methods to test #saveOn: by itself, by writing various objects and checking that you get the right bytes. But if the external representation is changed (and I need to change it), the tests for #saveOn: and #restore as such will have to be rewritten, while the tests for #saveOn: and #restore *together* will not. Cucumber offers an insight here, I think. A scenario in Gherkin is not a test case for an object. Nor is it a test case for a method. It is a test case for a composite *behaviour* of a system, at some contextually appropriate level of detail. Brian Marick had some lovely stickers. One of them reads "An example would be handy about now." I note that your blog post *did* provide an example of testing Date. In which none of your test cases used 'subject'. I entirely agree with you that the three methods have good intention-revealing names. What we actually need is some examples where 'subject' pays off. On Mon, 20 Jan 2025 at 04:04, Koen De Hondt <koen(a)all-objects-all-the-time.st> wrote: > > Dear Pharo users and developers, > > In my series of blog posts on testing, I added a follow-up post about a dedicated name for the object under test in SUnit tests, the âsubject". > > Happy reading! > > Ciao, > Koen >

Jan. 23, 2025

Re: New VM Release v10.3.3

by stephane ducasse

Thanks a lot for you dedication and positive energy around this important artefact. S > On 16 Jan 2025, at 10:27, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi all, > > Weâve published a new VM release (v10.3.3) to be used with Pharo versions 10 through 13. > > 10.3.3 includes all changes in 10.3.2 (that was rolled back) plus several improvements. > > Highlights: > - improves the naming schema of built artifacts to differentiate releases from intermediate/nightly builds > - is built on the old file server (that we recovered!) to support compatibility with older GLibC versions > - builds and run properly on newer linux systems (we fixed a couple of linking and compilation issues with newer versions of gcc) > - many improvements in the perm space > > Please find in the wiki information about the build and versions > > https://github.com/pharo-project/pharo-vm/wiki > > Full release changes log > https://github.com/pharo-project/pharo-vm/releases/tag/v10.3.3 > > Finally, a big thanks to MaxLeske and Norbert for testing, and to everybody who contributed even in the previous conversations. > > Cheers, > G StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

Jan. 20, 2025

"Subject in SUnit Tests" â New blog post on all: objects all: theTime

by Koen De Hondt

Dear Pharo users and developers, In my series of blog posts on testing, I added a follow-up post <https://all-objects-all-the-time.st/#/blog/posts/12> about a dedicated name for the object under test in SUnit tests, the âsubject". Happy reading! Ciao, Koen

Jan. 19, 2025