standardy testerskie
Take care of the high quality of your product

Are you planning to implement a new system? Make sure your product has been tested well!

Software testing is an important stage in creating any new solution. Testers can predict and prevent many problems, supporting correct functioning and ensuring the high quality of the developed solution. If you want to provide your users with a solution fully tailored to their needs, offering a high product quality, then the testing stage is a must on your implementation roadmap. A well-tested system also means trust and customer satisfaction as well as cost savings as the result of the high standard of your solution.

Are you looking for a partner who can test your solution? At Craftware, we employ certified ISTQB® specialists with multidisciplinary experience, among others, in the Salesforce and Veeva projects. Check us out!

Why is software testing important?
  • Increases confidence in the developed product
  • Indicates errors and defects during software development
  • Provides users with high-quality products and software
  • Reduces the cost of maintaining the application enabling resources’ allocation to product development
  • Minimizes the risk of failure
  • Ensures the effectiveness of the solution you are building
Our certificates
  • istqb-certified-tester-foundation-level
  • istqb agile
  • ISTQB-Foundation-Level
  • ISTQB® Test Manager
  • Veeva-CRM_assosiate-white-belt
  • Veeva-Vault-Platform_assosiate-white-belt
  • ITIL®4 Foundation
  • Salesforce-Certified-Administrator
  • Salesforce App Builder
Standard step-by-step testing process
    • Preparing a Test Plan and Test Strategy
    • Presenting the approach to creating test scenarios, executing tests, and reporting errors

    • Conducting status meetings
    • Coordinating testers’ work and tasks assignment
    • Verifying test scripts quality and reviewing errors reported
    • Inspecting tests coverage for system requirements
    • Planning, coordinating, and monitoring test progress

    • Preparing test scenarios
    • Performing tests based on scenarios
    • Recording testing results
    • Identifying defects and recording errors
    • Tracking bugs until they are fixed and closed

    • Summarizing performed activities and specifying the areas that have been tested
    • Test report based on the execution of tests conducted using a tool and an overview of fixed and open errors

    • Supporting the organization of acceptance tests (proposal of the approach, scope, and time needed to conduct them).
    • Supporting users during tests
    • Preparing test accounts
    • Selecting and adjusting test scenarios
    • Tracking reported malfunctions
    • Reporting on the progress of acceptance tests and their completion.

Do you want to test your solution?
Let us know – we are happy to help.
Natalia

Senior Account Manager

sales@craftware.com

Why us?
  • icon_dostep-do-wiedzy

    Certified experts

    80% of our testers are ISTQB Foundation Level certified

  • icon_cenny-czas-twoich-pracownikow

    Fast and flexible availability of testers

    we can provide both a testing team and individual testers, or testing coordinators

  • icon_latwe-zarzadzanie-danymi-klientow

    We serve 50+ customers

    we have over 12 years of experience in working with global customers from such industries as life science, pharmaceutical, automotive, and finance

  • icon-doswiadczenie-projektowe

    Salesforce and VeeVa experts

    we employ experts who have Veeva CRM, Veeva Vault, Salesforce Administrator, and App Builder certificates

Frequently Asked Questions
  • The mission and main objective of the International Software Testing Qualifications Board (ISTQB) is to continuously develop the profession of a tester and maintain a set of standards and solutions in the field of software testing. Certified software testers ensure we apply international standards and practices in the product testing process. Consequently, the testing process is in line with the best, proven methodology.

    • functional – also called black-box testing. This type of test focuses not on the technical details but on WHAT the system does. Such tests concern the visible behavior of apps or functionalities with which the end-user will deal with. The product performance is verified based on the pre-defined requirements, which should be met, provided documentation, and business logic. Also, the suggestions of a manual tester who checks the system and tries to guess the recipient’s expectations are essential. Functional tests can be executed at each stage (phase).
    • non-functional – can be defined as parameters determining. This type of test concentrates on HOW the system operates. It means measuring these features of a given product that can be assessed on a scale (such as the loading time of a page, a record creation time in an app, and so on). It is important to remember that, usually, parameters are not clearly defined in the documentation. Even if an app turns out to be perfect regarding its functionality, the end-user will not be satisfied with its use when the app is not user-friendly or not operating smoothly. Non-functional tests can be executed at each stage (phase).

  • Repetitiveness is automation’s great advantage. Assuming the correct implementation of automated tests, we can ensure that necessary actions will be performed the same on each occasion. Moreover, unlike humans, these tests work constantly without breaks for coffee, sleep, or weekend rest. 😉 However, automated tests lack some elements needed to thoroughly test an application: intelligence, intuition, and imagination. Automation supplements manual tests but cannot replace, for example, exploration tests or a technique based on error guessing, based on the tester’s experience, both in the context of the tested product and the tools used to create it.