As a Test Analyst at Infomentum, I generally follow a formal structured test process, one that is promoted by certification bodies such as ISTQB. It ensures that we adhere to the best practices and verify that the software under test meets our requirements. But is it always enough? In my experience, no. On occasion, a more experimental method of testing is a more suitable approach for that given project. Great news, it also fits nicely with an agile development cycle!
We developers love to use and create automated processes! If something is repetitive, we have an urge to write a bash script, a gulp/grunt task, etc. It is in our nature! If we can automate, we will automate.
Exciting news to share! We are launching a new MuleSoft Online Group dedicated to introducing Java Developers to the MuleSoft world.
Here is a challenge for you - how to create an API that retrieves data from a cloud-based system with no external APIs? In the situations like this, it would make a perfect sense to access the data via the system's UI using robotic automation bots. Your API can invoke a bot to read the required information. To implement this solution and enable APIs to Bots requests, we need an API-RPA connector.
Do you know many MuleSoft developers with MSc in Physics and Medical Engineering? Meet Olga Kepa - an example of how a career can change in a drastic way when you pursue your dream.
One of the main features of Oracle APEX is the Interactive Grid (IG). For those unaware, it works as a CRUD to interact with any data from the database. There are many great features readily available in the IG. Search is one of such out-of-the-box capabilities, which means no extra development is required!
Are you in the middle of working out your integration strategy and selecting a suitable platform? It's a serious and long-term commitment, so wouldn't it be great to test a chosen platform first? Validate it by building fully-functioning API integrations for your specific use case?
Testing is a critical part of software development, ensuring early detection of bugs or any other problems within your code. However, for most of us it's the less favorite activity; it feels tedious and often repetitive. Furthermore, creating test for a large block of code can be troublesome, especially for beginners.
In my experience, when working with Interactive Grid, most of the times, we need to open a modal popup to interact with selected records (single or multi selection). For example, let say we have an Interactive Grid listing some records and you want a button which bulk updates all selected rows with the same value.
Unit testing has always been an integral part of software engineering because it ensures that problems in the code are isolated and fixed long before they become an issue in production. With the introduction and adoption of Agile framework, unit testing has changed dramatically because of the test-driven development (TDD) methodology. TDD is a software development strategy in which unit tests are used to drive the development process. In this blog, I explain how to practice TDD and share some tips on how to write great unit tests using MUnit.