Setup Menus in Admin Panel

ITeLearn.com

AnyAUT Certified Tester AACT Free Training Day 02

Below content protected for ITeLearn Guest Members.

To access our free content as a guest, please register on http://itelearn.com/index.php?/register/GUEST. Once you sign-in, you can access our FREE content and also the Technical Forum.



AnyAUT Certified Tester 7-hours Free Training Download PDF here

  • vijay kumar

    Scenarios Login:

    a).Positive scenario
    1. User ID and Password are correct
    User Log in correctly.

    b).Negative Scenario:
    1. User ID and Password are in correct
    User couldn’t Log in.

    c).Exceptional Scenario:
    1. User ID and Password are correct
    User couldn’t Log in.
    Pre condition: System unavailable

  • Kavya Chitra

    I am unable to see Invite Trainee Link on InterAFT, only Notification link is visible.

    • Manoj ITeLearn

      For trainees only Notification is visible.

  • Sandeep Reddy

    i had a question that how we can say that it is a failure case. because pooja wrote the test case for negative scenario by entering the invalid username & password but it popup an error message. then how we can say that it is a failure case? we can say that it is a possitive case

    • Manoj ITeLearn

      Sandeep, For any scenario you have positive and negative test cases. Positive test case tests that system supposed to do like login with valid credentials. Negative test case where system is validated against invalid data.

  • Mukesh Rawat

    Hi Karthik,

    In Day 2 we discussed one Test Scenario for sending invites. Where we wrote different test steps to achieve this scenario. I can see most of trainees has question regarding Login page and error popping out there. As per me USER Login page is different test case altogether, where we may have different scenarios as page is having Login button and forget password button etc.

    Only question I have do we need to breakdown this test scenario into different test-cases so that we can test different combination like for User Login, selecting project and email invite validation. If that is the case then we need to do it for each scenario we will be going to test like for Notification, Trainee etc.

    Thanks,
    Mukesh

    • Manoj ITeLearn

      Hi Mukesh,

      Correct, We can write scenarios and based on scenario write various test cases including positive and negative test cases with detailed test steps.

  • yamini jyoshna

    Hi Karthik,

    Please let me know from yesterday class are testcases can be written like this
    Teststeps are part of testcases.So testcases can be–
    1.Register user can login with valid data(TestData- valid username,valid Passowrd)
    2.Register user cannot login with invalid data
    3.User should be able to “Generate link ” by selecting appropiate course
    4.Genearted link should be copy to clipboard and share to others.

    Thanks
    Yamini

    • Manoj ITeLearn

      Hi Yamini,

      These above four points can be considered as Test Case Name or Description. It can also be scenarios, you can write your test cases based on this. Which will include test steps with data as you mentioned.

  • Ain Shin

    How we see the lecture notes?

    • http://ITeLearn.com Karthik Kosireddi

      Ain shin – We will attach the notes for you to download after the training is done.

  • priyanka jagtap

    Scenarios Login:

    a).Positive scenario
    1. User ID and Password are correct
    User Log in correctly.

    b).Negative Scenario:
    1. User ID and Password are in correct
    User couldn’t Log in.
    2. User ID is correct and Password is not correct
    User couldn’t Log in.
    3. User ID is not correct and Password is correct
    User couldn’t Log in.

  • Sakshi Sharma

    Hi Karthik, Manoj,

    we wrote Test scenarios /cases for log in page, email invite etc…we do get error message on the screen in case of negative Test case.
    My only question – is this the time we can also write test case/s for the backend with expected result? Add another test case( when there is error) to check the reason before raising the defect? or wait for the build to receive then add backend cases to the existing Test cases. Thanks

Main Menu