The demand for profiq’s services from Silicon Valley based hi-tech companies is increasing. This brings new opportunities for technical talent in the Ostrava region. People started seeing us as a competitive alternative to existing IT vendors on the job market of the region, even before moving to Ostrava. Opening a new engineering center in Ostrava increases our dedication to being the alternative.
Most of all, we are now even closer (couldn’t be any closer than that 🙂 ) to university students to enable them to work on technically challenging projects. We welcome fresh graduates with IT background, who are eager to bring innovation in technology to life.
Please visit us to have a chat in person over a coffee or tea. We are interested in hearing from you and ready to share things that you may be interested in hearing about us. You can find us just next to Technical University of Ostrava at premises of Business Incubator on Studentska 6202/17, Ostrava – Poruba:
Here comes a testing focused article after a series of technical blogs! It is based on experience with projects managed through waterfall processes and it continues the series about tackling test complexity.
It is about a luxury that we so often ask for and we often don’t have in testing: to be involved early in the product development process. What does it mean actually to be involved early in the process? Why is it so important? And how does it help tackling test complexity anyway?
We have been exploring capabilities of integrating Liferay with Amazon’s S3 storage service set for documents library repository. In one of our previous article we have introduced the purpose of integrating Liferay with Amazon S3 and provided basic information on how to setup those 2 systems to talk to each other. Liferay’s introduction on document management discusses some of the common business use cases and I thought I could elaborate on those in more details with regards to Liferay’s use of Amazon S3 services. In below article I’ll try to describe use cases and features that you might come across when you start considering and using Liferay.
This article follows-up with the series of articles about tackling test complexity, adding a view on the importance of product knowledge, when coping with the complexity of testing. Let’s assume that you understand already, who your customers are;)
I managed testing of a large integrated suite of software products on one of my past projects. Each product had its years of individual history already, when the decision was made to release them as a suite. And each of them was quite complex on its own, even without considering integration with other products. The number of installation issues reported by customers started increasing to an unacceptable level after a couple of years of the products suite’s existence. The whole engineering organization became concerned about the issue. First hypotheses about the cause assumed that the released installer was defective or that the product documentation was unclear. These were not proven however. So, we decided to conduct a profound root-cause analysis.
Working patiently and passionately on implementing the strategy to deliver best-in-class Software Testing and Software Quality Assurance services to our customers and partners we see it paying off over the time. To be able to satisfy the increased demand from our clients for specialists in Software Testing, we are looking for Read more…
A problem you might face while extending the OpenDJ functionality with a plugin is to develop proper unit tests. OpenDJ comes with a set of tools to facilitate the testing, but since they are tightly integrated within the build framework, you might find it difficult to execute your unit tests from outside of the framework. This article will try to give you short guidelines on how to integrate and execute your tests.
Software complexity is one of the most significant challenges that a software tester may face. Testing software that is complex usually requires a breadth of knowledge and experience. The goal that the tester needs to accomplish with regards to complexity is: to test the software in a reasonable time and at a reasonable cost.
As an example, think about ways to test upgrades of a database system with the following support matrix that gives altogether billions of combinations to test. Can this test scope be reasonably covered? Maybe. Let’s see several techniques that can help addressing complexity.