📚 F is for […]

[rosie (Rosie Sherry)]

F is for flaky tests

What else?

[mahatheed (Mahathee Dandibhotla)]

Here are a few
Failover
Failure Mode
Fault
Fault Injection
Fault Tolerance
Feature
Feature Flag
Functional Testing
Fuzz Testing (Fuzzing)
Framework
File System
Frontend
Full Stack
Flowchart
Formal Verification
Function
Functional Requirement
Fork
Fetch
Finalization
Firebug
Flexbox
Flow Control
File Compression
Feature Creep
Factory Pattern
Free Software
Feedback Loop
File Transfer Protocol (FTP)
Flame Graph
Feedback
Fixed
Flaky
Finite
Fickle
Flaw

[shad0wpuppet (Konstantin Sakhchinskiy)]

Fuzzing
False Positive/Negative
Feature

[pmichielsen (Peet Michielsen)]

Failure - When a result does not meet the expected outcome

[mirza (Mirza Sisic)]

There is some TV show called F is for Family and I thought it called Fis Family

[saritha (Saritha R)]

F is for Feeling as in QA’s feeling about the feature/quality of the product

[fullsnacktester (Ben Dowen)]

F is for Flow, where to start, where to go, and how to get there? Users flow through your system, can you observe that? What can you learn from those observations? Are they getting stuck? Understanding your users flow, can bring huge benefits.

[conrad.braam (conrad)]

Friction
Too much and it’s a stability or usability bug, too little and it’s a security bug.