Test F-connect login integration with site
High level scenarios:
(CASE I). User uses same Email ID for creating account and F-connect login.
a. System must allow the user to do so.
b. Also, since the email ID is same, single account must be maintained for both F-connect and site login.
(CASE II). User uses different Email ID for creating account and F-connect.
a. Two separate account's must be created and maintained.
Low level scenarios:
(CASE I). User uses same Email ID for creating account and F-connect login.
1. User first creates site account. Uses F-connect to login at later point of time and _places order without updating his site account.
> This case, all details provided by user while creating account must be pre-populated on checkout page.
> User must be able to edit the same. Edited details except First name, Last name and Email ID, everything else must be updated in user's table and as well in order's table.
2. User first creates site account, updates the same on "My account" page and then places order.
> > This case, all the details provided by user on "My Account" page must be pre-populated on checkout page. Any updation must update only the order related table(no updation on user table).
3. User could first login using F-connect and then create account to place order.
> > This case, Checkout page must pre-populate Email ID, First name and Last name. And user must be forced to add other details - Password, Billing address, Shipping address, Credit card info in order to place order. This updation must update both user table and as well order related table.
(CASE II). User uses different Email ID for creating account and F-connect.
1. This case, user must be treated as two separate user. Thus, account and order must be maintained separately.
