There is my functional test

from rest_framework import status
from rest_framework.test import APITestCase

__all__ = ['OAuthTestCase']

ADDRESS_FOR_TEST = 'http://127.0.0.1:8000/api/v1/request/'


class ApiOAuthTestCase (APITestCase):

     def setUp (self):
         User.objects.create_user (username = user_name, password = user_password)

         self.my_message = {
             'grant_type': 'password',
             'username': "user_name",
             'password': "user_password",
             'client_id': "secret_ket",
             'client_secret': "clietn_id",
         }

     def test_token (self):
         response = self.client.post (ADDRESS_FOR_TEST, self.my_message)
         self.assertEqual (response.status_code, status.HTTP_201_CREATED)

When passing this test, error 400 appears. Can you please tell me how to access the response content from response?

POSTMAN, Soap UI are the best

We use a proprietary framework based on the REST-assured library and TestNG to automate API testing for our REST web services. I saw some api testing code which uses Thread.sleep(n seconds) to wait for a response to be returned. This seems wrong to me because the response times can vary. I believe that there should be a better way to wait for a response, i.e. wait only as much as necessary. Maybe I could poll every few milliseconds, or by use an observer (test)-observed (api) design pattern, or something else. I am not sure.

How do I wait for an api to return a response ?

This is what the code looks like:

@Test
public void doApiTesting() throws Exception 
{   
    framework.loginUser(User);
    framework.createNewData();//Takes some time.
    Thread.sleep(10000);
}

I appear to have discovered the issue.

A REST GET request to a URL using SoapUI follows different encoding rules to an HTTP GET request.

Smartbear were unable to provide a reason for the difference in behaviours

Software engineering has many design patterns, including Adaptors, Abstract Factories, Decorators etc. Test automation, as a branch of software engineering, can use same patterns but has also its own design patterns, to name a few:

• Page Object - wraps an HTML page, or fragment, with an application-specific API, allowing you to manipulate page elements without digging around in the HTML.
• Screenplay - originally invented to address limitations of Page Object pattern: an Actor have Abilities to perform certain Tasks composed of Actions that interact with Elements of a Screen
• Features and Testers - originally invented by Guava team to test collections: different implementations share similar Features, so one test (caller Tester) for a specific feature can be used to test multiply implementations. It can be used to verify output of end-to-end scenarios as well.

What are other design patterns specific to automating tests?

I am thinking more of design patterns related to object-oriented programming, describing relations between classes and interfaces.

I read through this and I don't quite get it. If I currently run my rspec capybara tests using chromedriver, how will I change that to xvfb ?

I see the examples like Xvfb :1 -screen 0 1600x1200x32 but I'm not sure how to integrate that into my actual UI feature specs.

Four years ago, when I was working for a telecommunication company; we used to have brainstorm sessions that we came up with testing ideas altogether. One colleague first introduced me with this Persona testing, a.k.a role-playing testing.

• The subject under test was a new heart-beating sensor application that had been integrated into a portable radio. Someone working as a loner is our intended customer, e.g. an electrician working in a remote location, a miner working underground.
• We found this Persona testing approach interesting so that we simulated an environment that would literally isolate a tester; he was wearing a red arm-band so no one was allowed to talk to him in office; he dressed up as an electrician and carried tools like an electrician in office; he needed to drop on the floor as well to test "man-down" function.
• We indeed noticed a few design flaws from this Persona testing;
• There was a shortcoming as well: this Persona testing was only done in office but this heart sensor function was supposed to be worn 24/7.

How did you invent, formalize and document the Personas?

• We collected as much information from our intended customers; how they go to work, where do they eat, how long do they stay outdoor, how long does it take for an ambulance to drive over and etc. It is not really an invention but rather a re-enactment.

• Sadly, we did not treat Persona testing very seriously and no document was produced.

What are the general advantages of Persona-based testing comparing to a more common Role-based testing ("administrator", "supervisor" etc)?

• Personas testing is more human-orientated; it is more likely to discover what the customers really want.

• The main difficulty is how to accurately role-play a Persona.

OSCP stands for Online Certificate Status Protocol, so you need to decode it via JSR223 Test Elements and Bouncy Castle libraries.

For instance add JSR223 PostProcessor as a child of the request and add the relevant script to decode the response and check its status.

See How to Load Test OCSP with JMeter article for more details including example code snippets.

I am using phatnom js driver for my selenium test cases to overcome the headache of chrome driver.I see it is taking lot of time to execute the test cases.I tried html diver prior to phantom.Since html driver has issues in finding elements I focused on phantom js.

The concern with phantom js driver is it takes lot of time to execute test cases.I set the logging to none to avoid unnecessary loggin in phantom Are there any ways we can avoid this time execution for test cases?.

Phantim js version :2.1.1
Selenium :2.52.0

Any help would be appreciated.

UI Automation (often refered to as UIA) relates to a set of interfaces designed to allow one programs to interact with or to control another via the screen, keyboard and mouse. The intention is to allow programs such as screen readers and alternatives to keyboard and mouse to be used with (almost) any application. Hence most applications can be used by people with impaired vision or dexterity problems (or more crudely put: people with disabilities).

Microsoft also support the MSAA interface (Microsoft Active Accessibility) which is an older interface with the same goals. MSAA was released with Windows 95 and UIA with Vindows Vista. See here for more about both.

Having got the UIA or MSAA interfaces to an application, other programs can interact with it. This includes automated testing. Test systems such as Microsoft's Coded UI use the UIA and MSAA interfaces of an application.

Most of the Microsoft application developement frameworks (such as Windows Forms, WPF and MFC) provide proper support for either MSAA or UIA. The problem is with custom controls. They need to include support for UIA or MSAA otherwise they will not work with the screen readers etc. I have not found any good documentation on how to write the required support code.

Finally I found answer for this just moved Response assertion under JDBC request[other screenshots are remain same]. Thank you all.

Note, this is specific to TestRail but some questions could be considered generic issues:

I have worked for a couple companies that have gone through the implementation of automation into TestRail. In each company, there has always been different practices of doing things.

• When you automate a manual test case, what do you do with the manual case and what do you do with the automation case?

  • example 1: Do you keep the manual test and just flag it as automated, if so do you point to the case ID in automation to have a link and add any other fields to the TestRail case? How do you keep it up to date if the test changes?
  • example 2: Do you delete the manual test and import the automated test in its place?
  • example 3: Do you keep both tests but flag the manual one as automated?

• What do you use the reference field for?

  • example 1: Do you use it to link the JIRA epic/story for the test case? how do you then link to the requirements?
  • example 2: Do you use it to link to the requirements, if so, what tool do you use?

• Most automated tests are WebDriver, API, etc., but do you include unit tests in TestRail?

• If I have a manual test that's been automated but not under each platform, what do you do?

  • example 1: Don't flag it as automated but make a note in the test stating it is automated for xyz platforms (or a separate test case field with automated platforms).
  • example 2: Flag it as automated and spin up a new test case for the non-automated platforms.
  • example 3: Not a concern, if it works on one platform, it should be sufficient.

• If you add automated tests to testrail that do not have a corresponding test case, where do you put them?

  • example 1: Use a section ID of the feature to place them where they should logically go.
  • example 2: Use a section ID of the feature but then have an 'automated' folder where they go.
  • example 3: Have a flag automation folder.

• How do you work around being reliant on testrail IDs?

  • example: if you migrate from a cloud solution to an on-premise solution, all of your IDs break. If each test case is linked to an ID, this would be thousands of code changes needed; or if a manual tester moves sections around to reorganize the group tree, it may break automation.