Manual QA in Greenice

Manual QA

Greenice is a small outsourcing company (50 people) from Kyiv. Since 2007, we have been developing custom web applications for clients from the US, Europe, Australia, and Asia. During this time, they created about 300 applications and websites: custom ERP, CRM, medical solutions for Physiotec and charity SmartGiving, eLearning ExchangeCME, crowdsourcing Arcbazar, price comparison sites Slankit, review sites NoCowboys and even a few hybrid mobile phones.

We are primarily strong in backend development (PHP and frameworks) and always try to solve the client's problem with the help of technology. Clients like this approach, so their number is growing.

Our requirements:

Must have:

- 1+ years of work experience tester in outsourcing/product/gamedev;

- experience in projects with complex business logic;

- knowledge of English from Intermediate (all sites and tasks from clients are in English);< /p>

- knowledge of testing techniques;

- ability to create test cases, checklists, test plans;

- understanding of site interface elements;

- basic knowledge of SQL, HTML, JavaScript

Nice-to-have:

- understanding of Agile, Waterfall, Scrum, Kanban work;< /p>

- experience working with bug-tracking systems;

- Completed ISTQB course;

- experience using PostMan for API testing and experience in auto testing (optional mandatory, but will be a plus);

Examples of daily tasks:

1. Comparison of the design layout and the implemented layout on the project. Identifying and fixing inconsistencies. Sometimes to pixel hunting. Desktop and mobile version. The list of supported browsers and devices is discussed separately depending on the project.

2. Functional testing: comparing how the project manager and the customer assumed how a certain function/option would work and how the programmer implemented it. Detection of inconsistencies.

3. At the stage of planning a new project/adding new functionality to an existing project: if the manager/customer does not thoroughly describe the future "feature", clarify and work out its implementation. Find out aspects of her work. So that the programmer clearly understands what to do, and the tester in the future understands how to work and how to test.

4. Regression testing: to make sure that the new functionality implemented by the developer does not disrupt, does not break the already existing operation of the system. Detection of such breakdowns.

5. Periodically there is a need to refer to the project database, to ask simple SQL queries there to search for relevant test data. And also connect to the project server with SHH and run crowns that cause certain events in the system, necessary for tests.

6. Subsequently, a partial transition to work with PostMan (for API testing) and auto tests.

Working in a cross-functional team (programmer(s), team lead, PM, QA engineer).

Plug cost: 1000-1500 USD