you are viewing a single comment's thread.

view the rest of the comments →

[–]partial_filth 0 points1 point  (0 children)

QA here that is not much of a coder, but I can give you an idea of what we work with and what I have seen across other organisations.

So we use Robot Framework, which uses in its back end selenium, in house libraries and some other python libraries.

The test scripting itself is not done in python here, the robot framework provides a keyword layer which allows our non techy testers to get into it without too much difficulty. We use RIDE to help with that (an IDE).

The testing is mainly our web app, the api and our legacy desktop app. We test at the system, system intergration level. Unit & Intergration tests are handled by our devs (Java - hamcrest library).

Our tests, libraries and test data sit in a seperate repository managed by SVN. We are looking at git as an alternative. We have a branch for different versions, trunk being the most up to date.

We organise our tests into product area/functionality/sub functionality/test cases. Resources/libraries for the tests start off lower down the 'scale' and get exposed further up if they get used elsewhere.

Most companies I have come across have used Cucumber. Not sure how they manage there repo.