Testing User Creation, Disabling, and Stale Sessions

By Bogdan Stefan Plesa

User lifecycle testing shows why adaptive investigation matters. Creation, authentication, disabling, and session revocation interact across time. A happy-path script can check every screen while missing the relationship between them.

What changes

Create a synthetic user and verify the durable identity, assigned role, and uniqueness rule. Establish protected access before disabling the account, preserve the session, then probe that same session immediately after revocation.

The FaST standard

Check every layer: UI status, identity record, fresh authentication, and established-session access. Differences are findings. The FaST reference deliberately includes a stale-session fault because a convincing workflow can easily miss it when actions occur in the wrong order.

FaST: Fully AI Software Testing — Concept and Paradigm, created by Bogdan Stefan Plesa.

Explore the open reference project, read about the author, and inspect the source notes and limitations. Prepared with AI assistance and reviewed for consistency with the documented FaST proposal.

Comments

Post a Comment

Popular posts from this blog

Fully AI Software Testing: Beyond Scripted Automation

By Bogdan Stefan Plesa A login test can click the right buttons and still tell us very little about the product. It may confirm that a familiar journey works while missing the changed redirect, the stale session, or the account that should no longer have access. Writing that script with an LLM changes how we produce the script. It does not automatically change how we investigate the application. FaST, my proposal for Fully AI Software Testing, starts with a different unit of work: the testing objective. An agent receives a goal, observes the application, chooses an action, examines the result, and decides what to try next. The intended output is evidence that helps us understand the product. “Fully AI” describes the operational delegation I want to explore. It does not mean that accountability disappears. People still choose the purpose of the investigation, the environment, the permissions, and the evidence needed for a release decision. An agent completing a task is not the same a...
Read more

The Architecture of Autonomous Agents in Software Testing

By Bogdan Stefan Plesa , creator of the FaST concept and paradigm. An autonomous testing agent needs more than a browser and a prompt. It needs an objective, observations, a restricted set of actions, and a defensible way to report what it learned. In FaST, my Fully AI Software Testing proposal, those responsibilities form an explicit architecture. The reference repository implements a compact version in Python. Its application is an in-memory model, so there are no real users, orders, or payments. The purpose is to make the boundary between an agent's choices and the evidence for its conclusions easy to inspect. One decision at a time The planner receives the current application snapshot and the history of observed actions. It returns one action. The runner validates that action against an allowlist before executing it. The resulting state becomes input to the next decision. In offline mode, the planner is a fixed sequence. In model mode, LangChain requests a structured resp...
Read more