Everything that marks as Required has been fixed, details are as follows:



Question 1.1.1:
from sare:
1. Test Scenario is missing for Agree with Terms & Conditions ( 2.1.1.3 )
> Fixed in F.30.

2. Test Scenario missing that reason can not be more than 200 chars (2.9.1.3)
> Fixed in F.70.

3. 6. No proper test scenarios for

a)  2.9.1.4  Disable Profile of Cheating Parent
b)  2.9.1.5 Disable Profiles of Cheating Child Students for the Cheating Parent
> Fixed in F.71 & F.72.



Question 1.1.2:
from winstips:

1. Spelling mistakes:  In Functional tests : questoins, acutal, TeseUser's, Tracko, Persmission, Robitics,  In Test Data : fo, 
> Fixed.

from sare:
1. Test scenarios from 1 to 16 does not match to an ARS number
> Appealed.

2. Separate scenarios will be good  for 2.2.2.1 Enhanced features

  a) There will be a special button on the user's unregistered profile to ask the application
      for account re-registration approval (like "Request an Approval to Re-register
      unregistered account).
  b) There can be also a hyperlink to request an approval to re-register unregistered
      account in the "Un-registration success e-mail", sent to the user of the un-registered
      account. The user can press that hyperlink to ask the application  for account
      re-registration approval.



> Fixed in F.48, F.49.



Question 1.1.3:
from winstips:
1. database server and application server integration tests: software name with version is missing
> Fixed in integration tests.

2. Wireframe page names  should be mentioned in Steps column.
> Not fixed as it's recommended.


from rajwirock:
1. In 2.1 you have to test when select "I don't agree" in "Agree with Terms & Conditions" page, it wonĄŻt go next page.
> Fixed in F.30, duplicate.

2. In 2.1 you have to check email is mandatory when user registration is in parent role.
> Fixed in F.31

3. In 2.2 you have to verify there have validation information when input any on donĄŻt Answer 1 field
> Fixed in F.50.

4. In 2.2 you have to test user can send Account Re-registration Request to System Admin
> Fixed in F.48.

5. In 2.9 you have to verify here have validation for Reason field
> duplicate. F.70.

6. In 2.9 you have to test there is disabled Profile
> duplicate. F.71,F.72

Question 1.1.7:
from sare:
1. Scenarios  25 to 29 can not be automated as CAPTCHA is randomly generated and
  validation is done after Register button is pressed

> Fixed by adding a note in the setup data.
