Your highway to high-tech
כרטיס הכניסה להייטק - דרך עולם בדיקות התוכנה QA
Recommendation
מה כותבים לנו על הספר
What do we know to do?
Digital courses to help you get into the hi-tech world
School-for high-tech entry, no queuing, no waste time and money. The courses include real and accurate knowledge from the field, secrets only those who have a practical experience of over 15 years can tell you.
Learn MoreThe book - your entrance ticket to hi-tech - 2nd edition - the fast way to an effective software tester
1. The book - your ticket to high-tech - 2nd edition - the fast way to an effective software tester The book that will lead you to the world of high-tech, to lead the team and the software testing department. In format: physical, digital and audio 2. Notes meetings for the manager and software QA tester
Learn MoreTraining and consulting + the red line service
Training and consulting - Physical software testing methodology Monthly digital subscription - "The Red Line" Open WhatsApp line for questions and consultation during the month, minimum annual subscription (12 months a year)
Learn MoreJoin the QAtest website mailing list now
Click Now and go-to sign up for free video and now for a limited time, after registering you will get access to the free introductory course
It is clear that the email address will not be moved to any factor and will be used only for materials from the QAtest site.
מהדורה 2 של הספר זמין למכירה מחודש - 10/2024
מהדורה מעודכנת הכוללת פרק נוסף בנושא :
בסיסי נתונים - SQL.
להזמנת הספר - ראה קישור בקטגוריה "מוצרים חדשים".
צוות QAtest מאחל בהצלחה,
הצלחה זו החלטה - ישר כוח !
About - Nati Hornstein
מודה לכם על שבחרתם להיכנס לאתר QAtest - האוטוסטרדה שלך להייטק !
המטרה שלי :
להאיר את הדרך לאנשים בעזרת ניסיון, מיקוד ועשייה שמביאה לתוצאות.
מאמין שכל דבר ניתן לעשות, דרוש רצון והתמדה, אם הצלחנו להגיע לירח, כל פעולה על הקרקע פשוטה. ולכן חשוב לעשות את תהליך הלמידה בחן וקלילות.
אנחנו כאן לפתוח לך את הדלת לעולם בדיקות התוכנה QA ולעבודה בהייטק, עולם ההייטק צומח בארץ בקצב מהיר, הדרישה לאנשי הייטק עולה מיום ליום, ולבדוקי תוכנה בעיקר,
תנאי עבודה טובים, בהמשך אפילו טובים מאוד וחשוב לדעת שניתן להתקדם במספר רב של מסלולים ומקצועות מעניינים בעולם פיתוח התוכנה.
המסלולים שלנו -
1. להכניס אותך להייטק ב 7 שבועות בלבד ולעשות הכל כדי שזה יקרה ואת/ה תצליח/י ! דרך עולם בדיקות התוכנה QA, שתופס תאוצה גדולה בשנים האחרונות. חברות רבות מבינות שרק על ידי תוכנה איכותית, יצליחו להתקדם וליצור פריצת דרך בעולם העסקי.
2. ליווי / אימון מנטלי וכלים שיתנו לך להוביל מקצועית בתחומך, נתי עוזר ומדריך בשיטת אימון מנטלי וכלי טרילותרפיה, לפרטים נוספים - לחץ כאן.
ב3 שנים האחרונות נתי מתנדב בעמותת "עולים ביחד" והחלטת לשתף בנסיון והידע שצבר במשך יותר מ 20 שנים בעולם מערכות המידע, לכל מי שרוצה לעבוד בעולם ההייטק ואנחנו פתוחים לכל שיתופי הפעולה שמטרתם לעזור לכל אדם לפרוץ קדימה.
"לא נוכל לפתור בעיות באמצעות אותה צורת חשיבה שהשתמשנו כשיצרנו אותם"
אלברט אינשטיין
בברכה,
נתי הורנשטיין
וצוות QAtest
מחוייבים להצלחה שלך, הצלחה זו החלטה !!
אהו מיטאקויה הויאסין
New products
Main categories
WE BRING QUALITY TO THE WORLD
Articles
One of the important issues in software testing is the documentation of the tests, without documentation, it is not possible to know which situations have been tested, whether the process has been properly covered, whether all end-cases have been tested, are the testing priorities correct? On the basis of the famous saying "You did and did not report - did not do", it can be said: Tested and not documented = Not tested.
Read More
Several options for building a software testing team in the fast business world, Each business body makes adjustments to the company's objectives.
Read More
In the next two weeks, we are about to finalize tests, the fifth version this year, not including emergency transfers and "cross-version" failures and emergency repairs ...... which are required .... During the tests, bugs are discovered which are documented and passed to the development team.
Read More
The amount of test types is large, we have made a division by subject here to facilitate and make some order... Good luck.
Read More
The testing process consists of five basic steps: designing the test project, designing test scenarios, performing the tests, testing the documentation and meeting the threshold conditions for the completion of the tests.
Read More
The choice is yours: Walk in a long and hard way or discover shortcuts. Spend 4 years gathering slow information or establish a mechanism An effective method that operates in an understandable manner and creates optimal testing planning.
Read More
Creating a analysis report on-LINE test results must be available and accurate, because this report is critical to the decision to increase to PRODUCTION.
Read More
Root Cause Analysis-Coping with problems not only symptoms. Article presented in the USA at the STAR Conference In Orlando (2008), and at conferences in Europe (2008, 2009). and won a great feedback.
Read More
Many times I have been asked this question and many times I have asked it myself. Nine out of 10 times the answer was: when you reach a deadline or when the project manager decides. This is of course a real and real answer, but is it the answer that we as QA managers and examiners need to look for?
Read More
A list of software and aids for a reviewer on the subject: Load Testing Testing and planning management Bug Management Web Checks Embedded Systems
Read Moreהרצאה בכנס Test Smarter
By Nati Horenshtion
in a rapidly evolving software landscape, effective testing and automation arein crucial for maintaining quality and accelerating delivery. This talk will explore the four essential pillars that underpin successful software testing and test automation:Optimal Test Planning and Script Writing: Strategies for creating efficient and effective test plans and scripts.
https://test-smarter.com/media/summit-24/
Lecture at the Bureau of Information Technology in Israel
A series of tools to lead in software testing
Questions and answers
What is a software reviewer's role?
The software checker has multiple thinking and responsibility types. Such as thinking about design, efficiency and inferior interface, etc.
The reviewer returns the findings to related people such as product manager and designers.
A software tester is called Quality control Quality assurance.
QA-Quality Assurance
A department that has the end to ensure the quality of the organization's functioning and products. Execution by work procedures and standards, management of its results, document control.
STR
STP
Document that provides a framework for a software testing project:
* Review of the system under review - what is planned to test in terms of QC.
* Method and content of tests.
* Required resources for testing - Training of testers, testing tools.
* Test management and interface management with other teams. * Control point and reporting.
* Risk control.
STD
SPR
Document development bug details.
* Document detailing the list of faults discovered during the tests. * The report lists closed and open faults in different sections: project / development team / hardware / open / closed.
Unit
Unit tests are software tests at the smallest system unit level (module) that verify the unit's proper operation.
Testing should take place after the initial writing of the module or after making specific changes.
The idea is to create a set of tests, which will cover all module activity, and its success will reasonably prove that the module is working properly. This type of testing is usually performed by developers and not by end users.
integration
Software integration testing is also called integration testing is one of the software tests designed to test the effect that a given part of a software has with other parts of it and with other software that it interfaces with, such as an operating system.
Integration testing is a phase during software testing where several individual modules are connected and connected to a system or subsystem, or to an external system.
The integration tests are usually performed after all unit tests have been performed.
Purpose The integration tests are to test the central functionality and performance of the system between the various items.
System
Testing the system as a whole, usually seeing the user of the system's capabilities.
Acceptance tests
Admissions tests are a set of tests that a customer or user sets for a product, and is designed to ensure that the product meets all of its needs and requirements.
Acceptance checks are usually performed by the product orderer, after the product has been delivered to the ordering party by the producing body.
Admissions testing is an integral part of quality assurance processes, and in software products - software testing.
functional
These tests are based on the requirements document and the characterization screen and aim to check that the system does what it needs and does not do what it does (valid and invalid testing).
Usability
Convenience testing and application design efficiency and accessibility for disabled people. For example: ease of use of menus, convenient navigation and site orientation.
GUI
Check the controls and fields on the screen. Good behavior, a format of fields, according to the legality defined at the screen level and not the business logic. For example: Checking minimum and maximum characters in the field.
Load
Verify server side response capability in server / client systems that many users are expecting at the same time. These tests focus on measuring response times and finding the "breaking point" of the system. Apart from "virtual users", we also test loads resulting from transactions and jobs that occur "in the stomach" of the system (not just business processes).
Performance
Product performance testing at various configurations and load levels, and performance measurement for documentation / comparison requirements.
regression
Validates the system activity after it has been modified. Verify that what worked has not been broken in the wake of the transfer of a version.
Compatibility
To verify the ability to integrate the software / component into an existing / new system (for example - compatibility of the software with operating system updates, different browsers, other software that the software should work with, etc.).
Alpha/Betha Testing
Tests performed by a defined user group are closed (alpha) or open (in cell) which use the product and report flooding errors while in regular use.
sanity
Basic testing that allows you to quickly and efficiently identify if the basic functionality of the product is working properly and the product is in stable condition.
Smoke
Another type of testing is designed to quickly identify the stability of the product, by early detection of malfunctions that indicate a serious failure of any component of the product. Unlike sanity tests, smoke tests are usually performed more intuitively and flexibly, and not necessarily according to predetermined scenarios.
BlackBox
בדיקות קופסה שחורה (באנגלית Blackbox testing) על פי ארגון ה-ISTQB הן 'בדיקות פונקציונאליות או לא פונקציונאליות המתבצעות ללא התייחסות למבנה הפנימי של הרכיב או המערכת'. זוהי שיטה להגדרת בדיקות ולא שלב במעגל החיים של המוצר. לפיכך ניתן לבצע בדיקות קופסה שחורה בכל אחת מהרמות של בדיקות התוכנה: בדיקות יחידה, בדיקות אינטגרציה, בדיקות מערכת ובדיקות קבלה.
בבדיקות קופסה שחורה מתייחסים אך ורק לקלט ולפלט שהבודק מכניס לתוך המערכת, והבדיקה היא שהפלט המתקבל או הפעולה שקרתה באמת זהה לצפי. בשל כך, רוב הבדיקות הנערכות במסגרת בדיקות אלו הן פונקציונאליות שכן בדיקות לא פונקציונאליות קשה יותר לבדוק במידה ואין יכולת לשנות את מצבה הפנימי של המערכת.
המשלים לבדיקות קופסה שחורה הן בדיקות קופסה לבנה, שהיא שיטה לבדיקת ההשפעה שיש לקלט או לפלט על המבנה הפנימי של המערכת.
White Box
Contact us
QA software tester - you have a resume, attach it and we will help you find a job (yes, free of charge and all purchase obligations)
Gallery
