check testnet.org for more info!!.

Not all software applications (information systems) are the same.

Some are OperatingSystem based, some are Web-based.

But even within the Web-based section they differ from one to another.
Because there are so many ways a software application can be build and what their core functionality is, there are also different types of test frameworks.

Examples of types of test frameworks are:
1. Linear Automation Framework
2. Modular Based Testing Framework
3. Library Architecture Testing Framework
4. Data-Driven Framework
5. Keyword-Driven Framework
6. Hybrid Testing Framework
7. Modularity-driven testing
8. Model-based testing
9. Code-driven testing
10. Behavior driven development
[read more]

So when choosing for a test tool. This is a good starting point to take this into account.

Related blogs: 
​https://www.maveryx.com/4-steps-to-select-the-right-test-automation-tool-for-your-project/www.maveryx.com/4-steps-to-select-the-right-test-automation-tool-for-your-project/

So I was thinking about this for a while....

The approach between project teams regarding software testing is many times not the same. Then suddenly I realized there's a analogy:
In some projects they have like a high gear... they start fast, but they don't do much unit testing and it seems like they finish 1 project-item (story) after another.

The other team however writes solid and proper unit tests and automation checks. They are more like in low gear... their velocity seems a lot lower...