Forum Discussion

smehaffieUMB's avatar
smehaffieUMB
Occasional Contributor
10 years ago
Solved

403 Error When Running Test In Test Suite

When I run a test it passes, but when I run all the test through the test suite Iget a 403 (Access Forbidden).  So why do the same test run when run directly but fail when run through the test suite....
nmrao's avatar
nmrao
Icon for Champion Level 2 rankChampion Level 2
10 years ago
Copy Link
Does test cases have dependency on other test cases?
smehaffieUMB's avatar
smehaffieUMB
Occasional Contributor
10 years ago
Copy Link

No, as stated in 2 previous emails all the steps run fine when I run the rest by itself but all the test fail after a certian number of test run.  So if I move the first test that fails up one place then it passes and the one it switched places with now fails.  All the test in this one Test Suite hit the same URL.

  • nmrao's avatar
    nmrao
    Icon for Champion Level 2 rankChampion Level 2
    10 years ago
    Copy Link
    In my openion, there could be two possibilities here.
    1. could be an issue with application that is under test. To avoid complexties/ isolate the issue, try to test manually in the same sequence where you notice problem.

    2. Something causing the interdepency or loosing the application state when the steps are interchanged.
    • smehaffieUMB's avatar
      smehaffieUMB
      Occasional Contributor
      10 years ago
      Copy Link

      I already did the test individual.  I can go straight down the list and run each test individual and they all pass, it is only when run together as a "test suite" that at some point all the test start failing.  But runnign them manually and they pass.

      • smehaffieUMB's avatar
        smehaffieUMB
        Occasional Contributor
        10 years ago
        Copy Link

        I found out what the issue was.  On our new Win2012 servers we had some setting setup to help stop DOS attacks. This cuased the test to fails after so many were runs successfully because the server saw the request as DOS attack because of the number of request coming from the same IP in such a quick manner.  We disabled this feature and that took care of the issue.