so, to achieve a particular number of users you first have to add a Thread Group or, better, a Concurrency Thread Group where you can specify your desired concurrency, say how many users you want JMeter to be simulating at the same time.
You can also configure some ramp-up params there, check the component's reference for more details.
To implement the described flow, then, remember this one thing, as @Ray Oei said in his comment: if you're trying to simulate interaction between user and a website (which typically happens through a browser), then keep in mind that JMeter is not aware of what's displayed on the web page. The only thing you can do with JMeter is reproduce some HTTP requests (samplers in JMeter's jargon) that can simulate the interaction above described by your steps.
Unless you create http requests for web pages and go through their content looking for what you want, scraping, doing regex extraction.
So first thing to do if you want to go with that is to figure out all the HTTP Requests that are needed and add them to the Thread Group, e.g.:
- Login to the web application. -> create an HTTP Sampler for a POST request to some login endpoint (probably need to create some users first or store credentials somewhere). You will probably need to add some kind of post-processor to get a session-token or something that allows you to make subsequent requests as a logged-in user.
- A landing page is displayed. -> You won't know that from Jmeter. You'll only be able to know if login was successful.
- Two options displayed. -> You won't know that from Jmeter. The only thing you can do is make a request (another HTTP Sampler) to some url that should render the expected page and scrape its content with some POST Processor (like Regex Extractor).
- Selecting one option, which will redirect to the specific landing page. -> You cannot "select" one option; once again, you need to figure out which url is called by selecting/clicking on that option, then create an HTTP Request sampler for that url.
And you go on like that.
So you'll have a thread group to simulate how many users.
Then you'll have multiple HTTP Requests/samplers to simulate the user's behaviour.
Once you're confident with that structure you can start grouping actions/samplers into controllers and control the flow with If Controllers or other components.
Here's an example: login, check balance; if balance low add money; then start getting data and posting data from / to the server.
Hope I cleared it out a bit.
Have fun :)
