Clarification: 2.3.1 "same user" " expected sequential step order" "without skipping steps"

[ajayojha]

Verify that the application will only process business logic flows for the same
user in the expected sequential step order and without skipping steps.

The modern systems are state driven not step driven. For verifying the parallel actions and concurrent workflows have other requirements under business logic security? as current requirement not covered the mentioned case.

"without skipping steps"
Absolute statement. even if business logic allows it then also it should not be skipped for example partial save.

"only process"
How QA verify this?

[elarlang]

Ignorable rhetorical questions: What is a "modern system"? How it is defined by the "industry"?

If business logic rules requires certain order of steps, it must be checked. What is the problematic part here?

[ajayojha]

What is a "modern system"?

Sorry, it's modern application/architectures like SPA, micro-frontent, microservices, state-driven application architectures, asynchronous pattern, event driven systems, etc.

How it is defined by the "industry"?

Please search above mentioned terms you will get lot more information in google search.

If business logic rules requires certain order of steps, it must be checked. What is the problematic part here?

The modern systems are state driven not step driven. if require more explanation to understand the context, I would be happy to share more information/use-cases.