devel:ARM:Factory:ARMv9

ARMv9 test build Current set of packages: Rings:0-Bootstrap + Rings:1-MinimalX + \+ few additional packages (audit a2ps buildah chromium cockpit-tukit cups-filters2 distribution distrobox docker-compose cJSON clamav container-diff cpupower crash dool dovecot dovecot24 elixir elixir -hex erlang ex_doc gn gv iftop ksh libcupsfilters libgpiod libppd lua-dkjson mariadb-connector-odbc mutt obs-service-docker_label_helper OpenCSD pam-test patterns-kde perf python-openqa_review python-humanfriendly python-pika rabbitmq-server release-compare rust1.93(for chromium) sshfs systemd-presets-branding-Aeon vhostmd vorbis-tools wdiff weechat znc) + \+ more images: kiwi-templates-Minimal + \+ containers: opensuse-tumbleweed-image busybox-image https://download.opensuse.org/repositories/devel:/ARM:/Factory:/ARMv9/standard/ openSUSE:Factory

The next openSUSE distribution

openSUSE Tumbleweed: The Bleeding Edge, Perfected. Tumbleweed is the ultimate rolling release distribution, providing the latest software as it’s released, built upon a foundation of world-class stability and testing. * Always Current: Get the newest kernel, IDEs, desktops, and applications automatically. * Powerfully Stable: Experience the velocity of a rolling release without sacrificing the reliability you depend on. * Engineered for Professionals: The top choice for Developers, Power Users, and openSUSE Contributors who need the best tools for the job. If you demand the latest stable software, your choice is Tumbleweed. Staging dashboard is located at: https://build.opensuse.org/staging_workflows/openSUSE:Factory List of known devel projects: https://build.opensuse.org/package/view_file/openSUSE:Factory:Staging/dashboard/devel_projects Have a look at http://en.opensuse.org/Portal:Factory for more details. https://download.opensuse.org/repositories/openSUSE:/Factory/ports/ perl-Test-Base

Data Driven Testing Framework

Testing is usually the ugly part of Perl module authoring. Perl gives you a standard way to run tests with Test::Harness, and basic testing primitives with Test::More. After that you are pretty much on your own to develop a testing framework and philosophy. Test::More encourages you to make your own framework by subclassing Test::Builder, but that is not trivial. Test::Base gives you a way to write your own test framework base class that _is_ trivial. In fact it is as simple as two lines: package MyTestFramework; use Test::Base -Base; A module called 'MyTestFramework.pm' containing those two lines, will give all the power of Test::More and all the power of Test::Base to every test file that uses it. As you build up the capabilities of 'MyTestFramework', your tests will have all of that power as well. 'MyTestFramework' becomes a place for you to put all of your reusable testing bits. As you write tests, you will see patterns and duplication, and you can "upstream" them into 'MyTestFramework'. Of course, you don't have to subclass Test::Base at all. You can use it directly in many applications, including everywhere you would use Test::More. Test::Base concentrates on offering reusable data driven patterns, so that you can write tests with a minimum of code. At the heart of all testing you have inputs, processes and expected outputs. Test::Base provides some clean ways for you to express your input and expected output data, so you can spend your time focusing on that rather than your code scaffolding.