You have built a product and want to make profit of it? You spent months on analysis, implementation, and on introducing fixes and new functionalities? Now, the number of changes has grown so that you start to wonder whether you haven’t missed a detail that can ruin the wow effect when you launch the product to market? Don’t wait and verify your tool with the help of a manual tester. Well-executed manual testing is a process which requires engineering knowledge and experience. At Craftware, we have them both, and in our work we focus mainly on the quality of the completion of tasks ordered to us.
Ensure high quality of a software
Make sure that the new product meets you expectations and is compliant with the requirements.
During product use simulation at the testing stage, you will make it more intuitive and user-friendly.
Avoid all unnecessary costs
Testing your product will let you avoid financial loss due to potential bugs.
Control changes in your product
Thanks to testing, you will ensure proper quality of changes appearing during maintenance.
- projects/products involving specialized knowledge;
- software development process (PoC, project phase);
- high-risk projects in which error classification can be dynamic;
- desktop tests (e.g. Java, C#);
- exploration tests which require tester’s experience and intuition;
- usability tests which enable to evaluate clarity and user-friendliness of given software;
- ad hoc tests which do not require thorough preparation as in the case of automatic tests;
- mobile application testing (iOS, Android, Windows Phone);
- processes preceding automatic tests;
- tools for test management (HP ALM, Jira, Visual Studio, Test Link, Azure Test Plan);
- non-functional testing (e.g. Jmeter);
- web application testing (Salesforce, JavaEE, CSS, HTML, SoapUI);
- tests of other tools (Atlassian Bamboo, SourceTree, GIT, Jenkins).
Analysis of requirements
We analyze requirements related to business goals presented by the customer.
We determine testing standards: the goal, scope, budget, time, team, testing approach, materials, risk.
We develop a testing plan by allocating resources: who will be testing, when, with what and where.
We prepare a testing environment and create test data.
Test task preparation
We create a list of test cases which will verify functionalities specified in the customer requirements.
We perform tests and verify whether customer requirements are met.
We record, categorize and analyze the deviations found.
We check whether the reported bugs have been fixed.
We confirm whether the applied modifications had no influence on other areas of application operation.
Access to the best experts
At Craftware, we employ 25 ISTQB Foundation Level testers.
Advanced knowledge of tools
We use a broad range of tools, including Jira, Testlink, HPALM, Workbench, Postman, Jmeter, Selenium.
Numerous projects in the portfolio
We have performed tests in many international projects, and gained experience in financial, pharmaceutical, medical and automotive industries.
Experience in integration tests
Salesforce to Salesforce, TIBCO, SAP, Agnitio, Third-party integrations from/to Salesforce.
Our aim is that after the implementation the customer is as independent as possible and has one or a few administrators who will be the internal line of support. However, companies often decide on our additional support so as to have an experienced partner at hand in more difficult situations.
Based on our experience, we recommend a Product Owner as the main role. The Product Owner is responsible for implementation at the customer side (responsibility for business and technical requirements, coordination of other people at the customer side, responsibility for future system maintenance and development). Moreover, in order to successfully complete a project, the following people must be included: project sponsor/sponsors (usually CEO, members of the Board), the owners of business processes which will be covered by the CRM, and the IT department (the architect who has comprehensive knowledge of the company systems, people responsible for individual systems that will be integrated with the CRM). Other important people are the Ambassadors (that is selected system end-users) and third-party vendors. In the case of integration with external systems, this can be also marketing agencies carrying out campaigns for the company (Salesforce Marketing Cloud, Audience Studio, Pardot).
Salesforce provides a possibility to integrate with any system, whether cloud-based or located in the customer’s environment. It can actively refer to other systems (call an API) and be referred to by other systems as well. Moreover, Salesforce has as an integration tool called MuleSoft which supports all integration methods available on the platform.