LOGIN
התחברות או הרשמה
להמשך הרשמה ידנית – לחץ על כפתור ההרשמה, להרשמה/כניסה מהירה בעזרת חשבון רשת חברתית – לחץ על הלוגו בכותרת
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 קרא עוד...
I'm in the middle of BBST Bug Advocacy at the Association for Software Testing right now. As you might imagine, on a course with that name there's been plenty of talk about what we mean by terms like bug, value, and quality. One of the great things about the four-week course is the mix of book work and application, so we students are repeatedly challenged with situations in which the learning can be practically applied.I have a lot of time for both Seth Godin and Shane Parrish so I'd have been listening carefully to Seth's appearance on the Knowledge Project podcast anyway but, given the context I'm in, the passage I've transcribed below stood out. It's about how the concept of quality is concretised as conformance to spec, and how that in turn directly drives physical actions. It starts at around 1:04:45:There's lots to be said about the spec. First lets talk about Edwards Deming and what spec and quality mean. Quality is not luxury, quality is not expensive, quality is not that you love it, quality is just one thing: it meets spec.So if I look under an electron microscope at any part of a Lexus, which is by any measure the highest quality car there is, it's filled with defects. But they're not defects that matter, because they're defects that are within spec.So, we begin by understanding what is the spec of the work we're going to do? If it meets spec, not only is it quality but[…]
בודק - הבן את המודל והאתגרים העיסקיים המוצרים אותם אנו בודקים מיועדים (בין השאר) לקדם את מטרות הארגון בו אנו עובדים, ולנו מחוייבות לעזור בתהליך זה, שהרי לשם כך בעלי העסק מחזיקים בארגון ומעסיקים אותנו, לעיתים…
הערכות זמנים הינן תהליך חשוב להצלחת הבדיקות לא תמיד יעזור להוסיף בודקים - זכרו "תשע נשים לא יולדות בחודש..." להוספת בודקים יש עלויות נלוות של הכשרה, ניהול ועוד. לעיתים קרובות ניתן לשפר היעדים מבלי לפגום באיכות…
