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
Well, as the title states we'll be addressing software development topics (mainly in English). Topics will be quick and short and most probably aligned with the training "problems", sorry, programs I am involved in. PS. Some links are "internal" (not publicly available): If you are not able to reach it, google will find you a publicly available information source for sure. Happy trails to you.
for all (x, y, ...)
such as precondition(x, y, ...) holds
property(x, y, ...) is true
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).
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.