quinta-feira, 19 de setembro de 2019

SW Testing: Introduction to Stateful Property Based Testing

Introduction to Stateful Property Based Testing - Lambda Days 2019



Quoting:

"Property-based testing (PBT) relies on properties which can be written in pseudocode as:

for all (x, y, ...)  
such as precondition(x, y, ...) holds  
property(x, y, ...) is true
Introductory examples usually illustrate the technique with testing a data structure or a function, by recording its inputs and outputs and checking that specified properties are all valid.
Few commonly known examples deal with stateful PBT applied to testing actual live systems. In his talk, Kowal gives such an example. The process involves the identification of properties, building a stateful model of the system under test (SUT), using that model to generate interesting test sequences, running the test sequences on the actual system, comparing at each step of the run the system behaviour and outputs to those predicted by the model, and shrinking failing test sequences to a minimal expression."

quarta-feira, 18 de setembro de 2019

SW Testing: Print Screens?

Oh, did I ever tell you you need to take (efficiently) print screens while (manual) testing? Some ideas towards productivity:
https://www.pcmag.com/feature/370572/how-to-take-screenshots-in-windows-10

PS: Also do not forget the utility "mouse without borders" also crucial for testers (with 2 or more PCs and just one mouse).

Documentation: Tracked changes in Google Docs?

Yes. It's called suggestions. Share with Edit permissions. Uncheck the email notifications. Much like MS  Office, comments also exist in Google Docs as well as a Compare option in tools and a revision history (with human readable names that can be set by the user):
https://www.pcmag.com/article/330137/tip-how-to-use-track-changes-in-google-docs

Missing TBC: The Combine (with generated inline tracked changes) option, much useful to know what words changed between 2 revisions when someone forgot (or "forgot") to start tracking changes. If you have PDF versions attempt a conversion of PDF to docx and then combine (Office does it).

Documentation IS part of the configuration of a software so, do learn to use productivity tools. This is why it's called productivity tools.

sábado, 14 de setembro de 2019

BOOK: NASA Systems Engineering Handbook, NASA - Amazon.com

Rev1 of SEBoK from NASA (caution, there is a Rev2 and the PDF can be found at NASA sites):

NASA Systems Engineering Handbook, NASA - Amazon.com

Quoting:
"This handbook consists of six core chapters: (1) systems engineering fundamentals discussion, (2) the NASA program/project life cycles, (3) systems engineering processes to get from a concept to a design, (4) systems engineering processes to get from a design to a final product,(5) crosscutting management processes in systems engineering,and (6) special topics relative to systems engineering. These core chapters are supplemented by appendices that provide outlines, examples, and further information to illustrate topics in the core chapters. The handbook makes extensive use of boxes and figures to define, refine, illustrate, and extend concepts in the core chapters without diverting the reader from the main information. The handbook provides top-level guidelines for good systems engineering practices; it is not intended in any way to be a directive."


PDF version: https://www.nasa.gov/feature/release-of-revision-to-the-nasa-systems-engineering-handbook-sp-2016-6105-rev-2

quarta-feira, 4 de setembro de 2019

SW Construction: Java 13

One of the most popular Enterprise Application Framework is being updated, again. Details here:


"Java 13 is released in less than a month. As usual I'm listing all the new performance features in the release, just as I now do every 6 months with each new Java version. The new features, the performance benefits from each feature, and how to use the feature.

Java 13 is pretty light on performance features, but one specifically is worth knowing about ... read on at ""

terça-feira, 3 de setembro de 2019

Metrics: Software Development Performance Index (SDPI)

Software Development Performance Index (SDPI) for measuring Agile Teams performance.
The concept and principle is described in this whitepaper of "The impact of Agile Quantified" (from the Software Engineering Institute, the organization managing the CMMI model: