Tên đầy đủ
Tạ Thị Thinh
Giới tính
Nữ
Ngày sinh
02/04/1984
Bằng cấp
Internal Auditor • IFoundation Level Certification PMP foundation • CMMI Appraisal team member certification ISTQB advanced 3 module TM TA TTA
Giới thiệu bản thân
Có 12 năm kinh nghiệm làm trong ngành CNTT, 5 năm kinh nghiệm đào tạo QA, Tester và chứng chỉ ISTQB foundation và advanced level. Là 1 trong số ít người ở Việt Nam đạt được trọn bộ 3 chứng chỉ ISTQB advanced level và có chương trình đào tạo ISTQB advanced hoàn chỉnh trong 1 năm
Ngôn ngữ
Tiếng Anh

TOIEC 540

Thông tin thêm
Số video
49 video
Số khoá học
1 khoá học
Số học viên
2 học viên

Danh sách video

  • 26:45

    Tạo game Flappy bird của Nguyễn Hà Đông dễ dàng bằng lập trình Scratch

    Gv Tạ Thị Thinh Đào tạo tin học cơ bản và nâng cao- Luyện thi ISTQB foundation và advanced- Dạy Tin học văn phòng- Dạy lập trình scratch

    22 lượt xem -

  • 35:36

    Hướng dẫn tạo Game chim bay ăn mồi và tránh ma bằng Scratch

    GV Tạ Thị Thinh đào tạo tin học cho trẻ em: - Dạy kỹ năng sử dụng máy tính - Tin học văn phòng word, excel

    29 lượt xem -

  • 23:02

    Hướng dẫn lập trình Game hứng bóng cho trẻ em

    GV Tạ Thị Thinh đào tạo tin học cho trẻ em: - Dạy kỹ năng sử dụng máy tính - Tin học văn phòng word, excel

    20 lượt xem -

  • 16:37

    Hướng dẫn lập trình Scratch để tạo bảng vẽ bút vẽ và màu sắc sinh động

    GV Tạ Thị Thinh đào tạo tin học: - Đào tạo tin học văn phòng word, excel, google sheet - Dạy lập trình scratch cho trẻ em

    12 lượt xem -

  • 18:43

    Hướng dẫn định dạng hiển thị về ngày tháng và tiền cho dễ nhìn

    GV Tạ Thị Thinh đào tạo tin học phổ thông, tin học nâng cao, luyện thi chứng chỉ tin học

    14 lượt xem -

  • 23:58

    Hướng dẫn định dạng excel đẹp, nhanh bằng thủ công hoặc dùng công cụ tự động

    GV Tạ Thị Thinh đào tạo tin học văn phòng, tin học nâng cao, luyện thi các chứng chỉ tin học

    11 lượt xem -

  • 15:46

    Hướng dẫn định dạng dữ liệu và bảng trong excel nhanh chóng và đẹp mắt

    GV Tạ Thị Thinh chuyên đào tạo tin học văn phòng, tin học nâng cao, luyên thi chứng chỉ tin học skype: ta.thinh0204, email: thinhtt0204@gmail.com

    18 lượt xem -

  • 26:14

    Hướng dẫn sử dụng Pivot table để tạo các báo cáo thống kê nhanh chóng, chính xác

    Hướng dẫn sử dụng tính năng Privote table trong Excel để thực hiện các tính năng thống kê, sắp xếp các giá trị theo nhiều tiêu chí khác nhau. Đáp ứng yêu cầu thống kê và đánh giá số liệu của dữ liệu. Xem thêm

    22 lượt xem -

  • 18:51

    Hướng dẫn tạo form trên Google để thu thập thông tin- Google Form

    Tin học văn phòng- hướng dẫn tạo form trên Google để thu thập thông tin- Google Form

    19 lượt xem -

  • 09:30

    Cách chèn smart Art vào word và Power point cho bài giảng sinh động

    GV Tạ Thị Thinh chuyên đào tạo về Tin học, công nghệ thông tin và các chứng chỉ

    22 lượt xem -

  • 19:12

    Quy trình soạn thảo và định dạng cho văn bản

    Học Word, excel, office- Quy trình soạn thảo và định dạng cho văn bản- hướng dẫn chi tiết cách định dạng 1 hợp đồng bởi Tạ Thị Thinh Đào tạo CNTT và microsoft office Xem thêm

    25 lượt xem -

  • 20:00

    Hướng dẫn lập trình game Octobus chơi trong đại dương xanh bằng Scratch

    GV Tạ Thị Thinh đào tạo tin học phổ thông, nâng cao, luyện thi chứng chỉ: - Dạy tin học văn phòng - Lập trình scratch

    7 lượt xem -

  • 09:27

    Hướng dẫn học ISTQB foundation- chapter 6- Tools support for testing by Ta Thi Thinh

    Chúng tôi tiếp tục gửi đến các bạn bản tóm tắt ISTQB foundation của chị Tạ Thị Thinh giảng viên 3 năm kinh nghiệm đào tạo ISTQBCHAPTER 6: Tools support for testing 6.1 Types of Test Tools (K2) data-driven scripting technique keyword-driven scripting technique Data files store test input and expected results in    table or spreadsheet data files store test input, expected results and keywords in table or spreadsheet   support capture/playback tools Writing script manually   6.2 Effective Use of Tools: Potential Benefits and Risks (K2) Risks of using tools Unrealistic expectations Underestimating Over-reliance Neglecting Vendor Open-source Unforeseen 6.3 Introducing a Tool into an Organization Ngoài ra bạn có thể download nhiều tài liệu hay khác về testing theo link sau: http://bit.ly/2r3szBD Xem thêm

    1,000 lượt xem -

  • 25:02

    Tóm tắt kiến thức luyện thi ISTQB foundation chapter 5 part 1

    Chúng tôi tiếp tục gửi đến các bạn bản tóm tắt ISTQB foundation của chị Tạ Thị Thinh giảng viên 3 năm kinh nghiệm đào tạo ISTQB CHAPTER 5: Test Management (K3) 5.1 Test Organization and Independence 5.1.1 Test Independence 5.1.2 Task of test leader and Tester Testing phase Test leader tasks Tester tasks Planning and control –          Plans, monitors and controls the testing activities and task –          Write or review a test strategy –          Coordinate the test strategy and plan with project managers and others –          Contribute the testing perspective to other project activities –          Plan the tests –          Decide what should be automated, to what degree, and how –          Introduce suitable metrics Review and contribute to test plans Analysis and design –          Initiate the specification, preparation, implementation and execution of tests –          Select tools to support testing – –          Analyze test basic –          Identify test condition Implement and execution –          Decide about the implementation of the test environment –          Set up adequate configuration management of testware for traceability –          Adapt planning based on test result and progress –          Create test specifications –          Set up the test environment –          Prepare and acquire test data –          execute and log the tests –          Automate tests –          Review tests developed by others –          Use test tools as required for monitoring Evaluation exit criteria and report –          Write test summary reports –          Monitor the test results and check the exit criteria –          Decide to stop testing or not –          Measure performance of components and systems Closed activity –          Gathering metrics and analysis –          Collect testware  and test environment –          Analysis lesson learned and improve process –          Contribute to analysis lesson learned 5.2 Test Planning and Estimation (K3) Test plan items: Scope Objectve Approach Criterial Schedule Resources Deliverable Metrics Risks Test plan template 5.3.1 Test Progress Monitoring (K1) 5.4 Risk and Testing (K2) Risk can be defined as the chance of an event, hazard threat or situation occurring and resulting in undesirable  consequences or a potential problem The level of risk will be determined by the likelihood and the impact Project risk Product risk A risk to the project’s capability to deliver products: Scope, cost, Time A risk to quality of product Quality Related to management and control of the (test) project, e.g. lack of  ATM  staffing, strict deadlines, changing requirements Directly related to the test object 5.5 Incident Management (K3)   Ngoài ra bạn có thể download nhiều tài liệu hay khác về testing theo link sau: http://bit.ly/2r3szBD Xem thêm

    984 lượt xem -

  • 17:17

    Tóm tắt ISTQB foundation chapter 5 part 2 by Ta Thi Thinh

    Chúng tôi tiếp tục gửi đến các bạn bản tóm tắt ISTQB foundation của chị Tạ Thị Thinh giảng viên 3 năm kinh nghiệm đào tạo ISTQBCHAPTER 5: Test Management (K3) 5.1 Test Organization and Independence 5.1.1 Test Independence 5.1.2 Task of test leader and Tester Testing phase Test leader tasks Tester tasks Planning and control –          Plans, monitors and controls the testing activities and task –          Write or review a test strategy –          Coordinate the test strategy and plan with project managers and others –          Contribute the testing perspective to other project activities –          Plan the tests –          Decide what should be automated, to what degree, and how –          Introduce suitable metrics Review and contribute to test plans Analysis and design –          Initiate the specification, preparation, implementation and execution of tests –          Select tools to support testing – –          Analyze test basic –          Identify test condition Implement and execution –          Decide about the implementation of the test environment –          Set up adequate configuration management of testware for traceability –          Adapt planning based on test result and progress –          Create test specifications –          Set up the test environment –          Prepare and acquire test data –          execute and log the tests –          Automate tests –          Review tests developed by others –          Use test tools as required for monitoring Evaluation exit criteria and report –          Write test summary reports –          Monitor the test results and check the exit criteria –          Decide to stop testing or not –          Measure performance of components and systems Closed activity –          Gathering metrics and analysis –          Collect testware  and test environment –          Analysis lesson learned and improve process –          Contribute to analysis lesson learned 5.2 Test Planning and Estimation (K3) Test plan items: Scope Objectives Approach Criterial Schedule Resources Deliverable Metrics Risks Test plan template 5.3.1 Test Progress Monitoring (K1) 5.4 Risk and Testing (K2) Risk can be defined as the chance of an event, hazard threat or situation occurring and resulting in undesirable  consequences or a potential problem The level of risk will be determined by the likelihood and the impact Project risk Product risk A risk to the project’s capability to deliver products: Scope, cost, Time A risk to quality of product Quality Related to management and control of the (test) project, e.g. lack of  ATM  staffing, strict deadlines, changing requirements Directly related to the test object 5.5 Incident Management (K3)   Ngoài ra bạn có thể download nhiều tài liệu hay khác về testing theo link sau: http://bit.ly/2r3szBD Xem thêm

    735 lượt xem -

  • 20:22

    Tóm tắt kiến thức ISTQB foundation-chapter 1- part 1 by Ta Thi Thinh

    Với kinh nghiệm giảng dạy ISTQB foundation suốt 3 năm, chị Tạ Thị Thinh đã tóm tắt lại các kiến thức cơ bản nhất cần phải nắm được cho từng chương bằng hình ảnh và các phương pháp dễ nhớ nhất. Sau là kiến thức tổng hợp ngắn gọn nhất của ISTQB foundation CHAPTER 1: Fundamentals of Testing 1.1 Why is Testing Necessary (K2) 1.1.1 Software Systems Context (K1) 1.1.2 Causes of Software Defects (K2) Why do faults occur in software? Software is written by human beings Who know something, but not everything Who have skills, but aren’t perfect Who do make mistakes (errors) Under increasing pressure to deliver to strict deadlines No time to check but assumptions may be wrong Systems may be incomplete Failures must be corrected in the software The cost of finding and fixing defects rises considerably across the life cycle 1.1.3 Role of Testing Rigorous testing of systems and documentation can help to reduce the risk of problems Contribute to the quality of the software system, if the defects found are corrected before the system is released Meet contractual or legal requirements, or industry-specific standards. 1.1.4 Testing and Quality (K2) –     Testing measures software quality –     Testing can find faults; when they are removed, software quality  is improved –     Testing is a part of quality assurance –     Measure the quality of software in terms of defects found for both functional and non-functional software requirements and characteristics –     Give confidence in the quality of a software if it finds few or no defects and we have good test designs –     Improve the quality of future system 1.1.5 How Much Testing is enough? (K2) It depends on RISK –     Risk of missing important faults –     Risk of incurring failure costs –     Risk of releasing untested or under-tested software –     Risk of losing credibility and market share Risk of missing a market window Risk of over-testing, ineffective testing Test time will always be limited – Using RISK to determine –     What to test first –     What to test most –     How thoroughly to test each item –     What not to test ( this time) –     Allocate the time available for testing by prioritizing testing 1.2 What is Testing? K2) –     Test activities exist before and after test execution: planning and control, choosing test conditions, designing and executing test cases, checking results, evaluating exit criteria, reporting on the testing process and system under test, and finalizing or completing closure activities –     Testing also includes reviewing documents (including source code) and conducting static analysis. Test Objectives: Finding defects Gaining confidence about the level of quality Providing information for decision-making Preventing defects Prevent defects –     Designing tests early in the life cycle can help to prevent defects from being introduced into code. –     Reviews of documents (e.g., requirements) and the identification and resolution of issues also help to prevent defects appearing in the code. Different objectives in different phase –     In development testing: find as many defect as possible –     In acceptance testing: confirm that the system works as expected, to gain confidence that it has met the requirements. –     In some cases: assess the quality of the software to give information to stakeholders of the risk of releasing the system at a given time. –     Maintenance testing often includes testing that no new defects have been introduced during development of the changes. –     During operational testing: assess system characteristics such as reliability or availability. Debugging and testing are different. –     Dynamic testing can show failures that are caused by defects. –     Debugging is the development activity that finds, analyzes and removes the cause of the failure.. –     Re-testing by a tester ensures that the fix does indeed resolve the failure –     Testers test and developers debug – 1.3 Seven Principles of Testing Testing shows presence of defects –     Testing can show that defects are present, but cannot prove that there are no defects. –     Testing reduces the probability of undiscovered defects remaining in a software but, even if no defects are found, it is not a proof of correctness Exhaustive testing is impossible –  Test everything ( all combination of inputs and preconditions) is not feasible –  Instead of exhaustive testing, risk analysis and priorities should be used to focus testing efforts Early testing –  Testing activities should start as early as possible and focus on defined objectives – Perform the test design and review activities early can finds defects early on when they are cheap to find and fix Defect clustering – A small numbers of modules usually contains most of the defects discovered during pre-release testing, or is responsible for most of the operational failures – Rule 80/20: Module core often contains 80% defects Pesticide paradox – If the same tests are repeated over and over again, no new defects can be found – To overcome this pesticide paradox, test cases need to be regularly reviewed and revised; – New and different tests need to be written to exercise different parts of the software to find potentially more defects Testing is context dependent – Testing is done differently in different context – Ex: Safety-critical software is tested differently from an ecommerce site Absence of error fallacy – Finding and fixing defects does not help if the system built is unusable and does not fulfill the users’ needs and expectations 1.4 Fundamental test process 1.4.1 Test Planning and Control (K1) Test planning is the activity of defining the objectives of testing and the specification of test activities Test planning tasks: –           Determine the scope and risks and identify the objectives of testing –           Determine the test approach –           Implement test policy and/or test strategy –           Determine the required test resources –           Schedule –           Determine the exist criteria Concepts: –           Test policy: A high level document describing the principle, approach and major objectives of organization regarding testing –           Test strategy: A high level description of the test types to performed –           Test approach: The implementation of the test strategy for a specific project –           Test ware: includes test cases, test plan, test data Test control is the ongoing activity of : –           comparing actual progress against the plan –           reporting the status, including deviations from the plan. –           taking actions necessary Test control task: –           Measure and analysis the results of reviews and testing –           Monitor and document progress, test coverage and exit criteria –           Provide information of testing to make evaluation –           Initiation corrective actions 1.4.2  Test Analysis and Design is the activity during which general testing objectives are transformed into tangible test conditions and test cases. Test Analysis and Design tasks: –           Reviewing the test basis –           Evaluating testability of the test basis and test objects –           Identifying and prioritizing test conditions –           Designing and prioritizing high level test cases –           Identifying necessary test data to support the test conditions and test cases –           Designing the test environment setup and identifying any required infrastructure and tools –           Creating bi-directional traceability between test basis and test cases 1.4.3 Test Implementation and Execution (K1) is the activity where test procedures or scripts are specified, the environment is set up and the tests are run Test Implementation and Execution tasks: –           Finalizing, implementing and prioritizing test cases –           Developing and prioritizing test procedures, creating test data, writing test scripts. –           Creating test suites from the test procedures for efficient test execution –           Verifying that the test environment has been set up correctly –           Verifying and updating bi-directional traceability between the test basis and test cases –           Executing test procedures either manual or automate –           Logging the outcome of test execution –           Comparing actual results with expected results –           Reporting discrepancies as incidents –           Repeating test activities in order to confirm a fix 1.4.4 Evaluating Exit Criteria and Reporting (K1) Evaluating exit criteria is the activity where test execution is assessed against the defined objectives. This should be done for each test level –           Checking test logs against the exit criteria specified in test planning –           Assessing if more tests are needed or if the exit criteria specified should be changed –           Writing a test summary report for stakeholders 1.4.5 Test Closure Activities (K1) Test closure activities collect data from completed test activities to consolidate experience, testware, facts and numbers. –           Checking which planned deliverables have been delivered –           Closing incident reports or raising change records for any that remain open –           Documenting the acceptance of the system –           Finalizing and archiving testware, the test environment and the test infrastructure for later reuse –           Handing over the testware to the maintenance organization –           Analyzing lessons learned to determine changes needed for future releases and projects –           Using the information gathered to improve test maturity 1.5 Psychology of testing Level of independence –           None: tests designed by the person who wrote the software –           Tests designed by a different person –           Tests designed by someone from a different department or team ( e.g test team) –           Tests designed by someone from a different organisation ( e.g agency) Communication about defects –           Testing is very constructive in the management of product risks. –           Looking for failures in a system requires curiosity, professional pessimism, a critical eye, attention to detail, good communication –           Need good interpersonal skills to communicate factual information about defects –           Communicate findings on the product in a neutral, fact-focused way without criticizing the person who created it. –           Explain that by knowing about this now we can work round it or fix it so the delivered system is better for the customer. –           Start with collaboration rather than battles.   Ngoài ra bạn có thể download nhiều tài liệu hay khác về testing theo link sau: http://bit.ly/2r3szBD Xem thêm

    1,077 lượt xem -

Khoá học

22 bài | 90 phút 99.000 vnđ

[Đăng ký ngay] Đào tạo và luyện thi ISTQB foundation

Khóa học gồm 22 video ôn luyện 6 chương theo sách ISTQB foundation và syllabus. Ngoài ra có kèm các bài test online giúp các bạn luyện thi thành công và dễ dàng lấy được chứng chỉ

Tạ Thị Thinh Tạ Thị Thinh