Kategorie: Qualität

What is inside this edition –

• Being Bold as a Tester – Lisa Crispin
• A Fake Tester’s Diary
• How to Test: Writing Kick-ass Defect Report – Mike Talks
• Interview with Daniel Knott by Srinivas Kadiyala
• Building A Better Mobile App with the Right Testing Strategy – Kapil Saxena
• The Digital Test Center of Excellence – Wolfgang Platz
• Inclusive Design Really Is for All of Us – Michael Larsen
• #Testers2Follow @Twitter
• Book Worm’s Corner
• New NeoSense With Easy-to-read Reporting
• Perfecto Mobile Expands Focus To Digital Experience
• SOASTA Announces CPI To Measure Website Performance

UniTEE stands for Unified Test Engine Exemplified, and is pronounced as /ˈjuːnɪti/ (unity). It is spelled as Unitee elsewhere.

It is a test automation engine developed by Rahul Verma, with one key goal: Unification. It targets unification of different types of test case writing, for different types of test automation, at different layers, in different languages, for different purposes, applied in different development models, for different kinds of products and so on.

Unitee derives some elements of design for its test components from the excellent xUnit architecture by Kent Beck. Some key inspirations are the concept of fixtures, the default assertions and the XML result format. This indicates the impact xUnit architecture has had on Rahul as well as one of the goals of Unitee as being consistent in API to what developers & testers are used to for basic operations.

The similarities end here. A fundamental deviation which Uniteetakes is that unlike most of the Java based automation frameworks out there, it does not use JUnit as its base. It has been coded from scratch. It targets keeping easy things as easy as possible and making complex stuff much easier, as the latter is where many frameworks get it wrong.

In short, Unitee is a research project to serve software testers, developers, educationists and students. The goal is to develop an engine which can provide an alternative to existing test engines like JUnit, TestNG etc. This is especially true for the problem contexts, where it aims to serve better than existing engines.

Source: http://www.rahulverma.xyz/unitee-unified-test-engine-exemplified/

Dann aber brach etwas über uns herein, was man „QM“ nannte, „Qualitäts-Management“.

Keiner wollte es und jedes Unternehmen, das ich gut kenne, resümiert freimütig, daß sich die Qualität seiner Produkte mit der Einführung von Qualitäts-Management nachhaltig verschlechtert habe. Nun gibt es mindestens zwei Methoden, mit so etwas umzugehen:

Die Russen und die Italiener beispielsweise pappten einfach ihre DIN/ISO-Plaketten auf ihre Produkte und gut war es – genau wie die UL- und CE-Zeichen. In Deutschland geht so etwas nicht. Da wurden Hunderttausende Flachpfeifen, die nie im Leben gearbeitet hatten, zu ‚Qualitätsbeauftragten‘ „ausgebildet“, die in der Folge die abstrusesten Regularien verfaßten, die mit dem Verwendungszweck des Endproduktes nichts, aber auch gar nichts mehr zu tun hatten, aber die Produktion weiter verteuerten und so den Standortnachteil Deutschlands weiter verschlechterten.

(…)

Lutz „Luigi“ Colani ließ sich seinerzeit zu dem Bonmot hinreißen, „VW ist ein Misthaufen, auf dem der [Carl H.] Hahn sitzt“. Jeder intelligente Mensch, der es wissen wollte, wußte: VW ist das automobile Pendant zu Microsoft, für Menschen ohne Kultur, Verstand, Geschmack und eigenes Urteilsvermögen.

Quelle: IF-Blog » Blog Archiv » Mein Freund, der Softwarebetrüger …

Boah, da kann einer echt vom Leder ziehen. Sehr interessante Einblicke! Der andere Absatz erklärt mir wenigstens warum ich mit VW nie etwas anfangen konnte 🙂

07/10/2015

Today EFETnet’s electronic Regulatory Reporting service (eRR) for REMIT reporting went live. The go-live is in time for the REMIT Phase 1 reporting requirement, mandatory as of today. (…) This achievement is the successful result of a period of extensive testing in partnership with the Market Participants (MPs), Organised Market Places (OMPs) and ACER.

Quelle: eRR service for REMIT reporting is live today | EFETnet

What does testing look like without test cases? – Kim Engel

Source: Testing Trapeze – 2015 – August Edition – Testing Circus

Testing Trapeze and Testing Circus magazines 8/2015 are out and very nice articles are in both. I have talked last week to a release manager about testing metrics and that they are needed inside a huge organisation….hmm…. yes, but….

„I’ve learned a powerful secret in my quest to stop reporting on testcase
metrics: management appreciate bullet points almost as much as
graphs! So I keep my test reports short, useful and relevant.“

(Kim Engel, Testing Trapeze 8/2015)

I could sign that sentence because metrics create visible points but won’t tell the whole story. Daily stand-ups, verbal communication to the stakeholders (mostly also upper management) gives often more information beyond the numbers: They could give a forecast and the management is able to plan actions – hey, that’s what they always want!

Yes, metrics are indicators but you have to select metrics very well because team members will try knowingly or unknowingly to get save against the „rules“. The better approach is to give the team members a quality mindset which they are willing to follow and which actions / tasks they should fulfill to get quality product. Then a metric is just a quality control and testers will have more time for the deeper test scenarios instead of getting the basics done.