Creating a SQL Server cluster starts with cluster validation.
The SQL cluster installation will fail if the validation is not performed.
A rudimentary failover test could be to run a query against the master database before and after a simulated failure.
There will be warnings if you need to skip any validation tests as I did, but those warnings will not prevent installation of the SQL cluster as failures will.
At the Product Updates screen select the Include SQL Server product updates checkbox.
Here we see that Disk 1 is qualified, and Disk 2 is not.
Disk 2 is not qualified because it is reserved as the Quorum disk. In the Cluster Network Configuration screen select the IP type you want to use for cluster communications.
In our example we only have IPv4 enabled, and that is the one I selected.
It is not a good idea to use DHCP to manage the address here, so that selection has been left deselected.
Finally, enter an IP address, which will be used for the SQL Server network name that you entered in the Instance Configuration screen. In the Server Configuration screen you need to add a domain account for each service under the Account Name column and be sure to enter the password as well.
Do not change the startup type, as the SQL cluster will handle the startup of the services.
Allow the Setup Suport Rules screen to complete and click OK when the checks have completed.
If there are any errors click the Show Details button, correct any errors, and click the Re-run button before clicking OK to continue.
You can then check the Failover Cluster Manager and see the SQL Server role has been added to the cluster.