• The aim of testing is not to pass all of the tests

  I was recently working at a company where a developer, helping out on the testing activities, asked whether the aim of our (lightweight) test suite, hosted on the excellent Testpad, was to pass all the tests. So here’s a thought. What if the aim is not to pass the tests, but to execute them, to find out if they are broadly functioning as expected, and what else you can see while executing the testing. That is to say, using them as a guide, not a set of comprehensive instructions. The aim is to gather information that may prove useful to someone to know whether there are any risks that they should know about. For this reason, the tests are lightweight, e.g. “Check X functionality.” This allows the scope for 1. confirming that it works against the specified requirements (hosted elsewhere, usually in our JIRA and design docs), 2. checking the visual implementation against design specifications, and 3. anything else we feel is important, at our own discretion, and using our learnt experiences and intuition. This could lead to testing security with some code injection, reviewing the accessibility, spell-checking the copy, or whatever else comes to mind that might result in exposing some level of risk. Maybe nothing comes of it, but if you don’t try, and something does get exposed, you wouldn’t have known. Can you really take that chance by sticking only to a very prescriptive Gherkin-style test script? And is it satisfying to do that, and only that?[…]

  26.02.2021 | 6:04 קרא עוד...

• Exploring Kafka

  Message brokers such as Kafka are very popular back end technology that testers may encounter, especially in a microservices based product architecture. Message brokers and message queues differ from API based request and response services in that the component subscribes to messages that could arrive at any time rather then specifically GET some data. There is a good introduction to Kafka and the concepts of event streaming here : http://kafka.apache.org/documentation/#introduction Let’s start exploring. Firstly, you’ll need to install Docker, which is a container virtulization platform. Once installed, clone the repository from https://github.com/ObjectiveTester/AllThingsTesting.com-examples.git and open a terminal in the same directory as docker-compose.yml: AllThingsTesting.com-examples/Kafka And type the following commands: docker-compose up -d docker-compose exec kafka bash This downloads, installs and starts the necessary Kafka components, and starts a terminal session on the Kafka broker so we can issue commands to it. In an additional terminal, run this command (as before, in the same directory as docker-compose.yml): docker-compose exec kafka bash Produce and consume In the first terminal, create a message topic with: kafka-topics --create --topic simple-topic \ --bootstrap-server kafka:9092 \ --replication-factor 1 --partitions 1 Then run a command that accepts input to create messages: kafka-console-producer --topic simple-topic \ --broker-list kafka:9092 \ --property parse.key=true --property key.separator=":" In the other terminal, run a command to read a specific number of messages: kafka-console-consumer --topic simple-topic \ --bootstrap-server kafka:9092 \ --consumer-property group.id=test-group \ --property print.key=true --property key.separator=":" \ --max-messages 2 In the producer terminal, type in line by line (or copy and paste in one[…]

  26.02.2021 | 2:00 קרא עוד...

לרשימה המלאה >>