salvador4k: (Default)
"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live."
- Martin Golding

“The trouble with programmers is that you can never tell what a programmer is doing until it’s too late.”
- Seymour Cray

"Measuring programming progress by lines of code is like measuring aircraft building progress by weight."
- Bill Gates

"Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code."
- Christopher Thompson

"Perl – The only language that looks the same before and after RSA encryption."
- Keith Bostic

"Python's a drop-in replacement for BASIC in the sense that Optimus Prime is a drop-in replacement for a truck."
- Cory Dodt

“The object-oriented version of 'Spaghetti code' is, of course, 'Lasagna code'. (Too many layers)."
- Roberto Waltman.

"I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone."
- Bjarne Stroustrup
salvador4k: (Default)

Добрый день всем интересующимся
В соответствии с многими вопросами и большой заинтересованностью, решил таки поделиться с вами намеченной программой намеченного курса, который таки да откроется в намеченное время

Курс будет проводитсья на русском или иврите, по желанию заказчиков.
Весь материал, ессно - только на инглише, но программка курса есть и на иврите, если кому-нибудь больше по душе.

Предлагаю все замечания в комментарии.
Готов буду прислушаться к мнению других, так что у вас реально есть еще последний шанс изменить программу некоим образом.


The main objective of the course is training the attendee to become software quality assurance professional, in terms of:

  • Becoming familiar with software testing and quality assurance as integral part of software development process, methodologies, terms and abbreviations used in the field
  • Acquiring ability to analyze requirement specifications documentation and render it into high level testing planning and design (STP / STD) and afterwards into low level test scenario preparation (STD / ATP), while maintaining traceability between requirements and test outcome
  • Obtaining basic knowledge in popular process enforcement and bug tracking tools
  • Gathering practical experience in popular tools and software used during software testing activities
  • Practical experience in performing quality assurance of distributed client-server systems.

Course Prerequisites

  • User level experience in Microsoft Windows working environment
  • User level experience in Linux / Unix CLI working environment – recommended
  • Academic degree – recommended
  • Previous experience with software development – recommended
  • Кnowledge of TCP/IP networking – recommended
  • English Knowledge on a technical reading level


Introduction to Software Testing and Quality Assurance

This section main purpose is to introduce the attendee to the world of software development as a process, with emphasis to be done on the quality assurance tasks, responsibilities and influence.

  • Basic terms and abbreviations
  • Software development models and life cycles (Waterfall, Sashimi, Spiral, V model, Agile) in conjunction with authorities responsible for each phase in the cycle
  • Quality Assurance as part of software life cycle
  • Quality assurance methods (black-box testing, white-box testing)
  • Software testing phases (unit, component, integration, system, acceptance testing)
  • Test types and objectives (Functional, Interface, Compatibility, Availability, Performance, Compliancy, Usability, Stress and Longevity etc.)
  • Software testing strategy, phases and transitions (requirement specifications, planning, design, implementation, testing, reporting, maintenance)
  • Final exercise

Software Test Planning

The section uncovers accepted methodologies for preparation of STP documentation.

  • Guidelines of successful test planning – how, when, and what to plan
  • Interaction with different authorities during planning phase
  • Review of main subjects to be considered during test planning
  • Functional breakdown of planned system
  • Known pitfalls from practical experience
  • Hands-on experience in software test planning (real life example)

Software Test Design – Getting Into Nuts’n’Bolts

The section covers the main aspects of transition from theory to implementation, describes the accepted methodologies used for preparation of (S)TD documentation.

  • Guidelines of successful test design – templates, considerations
  • Interaction with different authorities during design phase, testability evaluation
  • Definition of successful test scenario
  • Functional testing plan for Black Box testing – boundary values,  error guessing, decision tables, equivalence partitions
  • White box testing – Statement coverage, Code review
  • Handling Non-functional requirements
  • Known pitfalls from practical experience, requirement “reverse-engineering”
  • Hands-on experience in software test design (real life example)

Software Test Running and Reporting

The section describes the common methods used for execution, collection of test results and analysis, actual quality metrics and key performance indicators

  • Test lab preparation and environment freezing
  • Compilation of test cycles, planning and management of version transitions
  • Test Suites - efficient execution of test scenarios
  • Defect submit, life cycle, management and follow up
  • Efficient interaction with different authorities during test execution
  • Evaluation of Exit criteria and reporting
  • Test closing activities
  • Known pitfalls from practical experience, prioritization and show stoppers

Availability and Recovery testing

The section describes the main purpose of those tests as a crisis-preventive measure

  • Terms and Abbreviations (MTBF, MTTR, MDT, availability levels)
  • Outcomes of recovery-untested system failures
  • Main subjects to be suspect for testing and assuring recovery success (hardware, backups, DB)
  • Recovery on different architectures

Interface & Conformance testing

Each software application has at least 1 interface towards other authority, be it human or another application. The section concentrates on main interface types

  • Human ó Machine interface – usability, design, functionality
  • Machine ó Machine interface – conformance and compliancy, security, error handling
  • Client-Server communication models (Thick Client / Thin Client)
  • Pitfalls
  • Hands-on Experience

Testing of Non-Explicit requirements

Requirement specifications will never be 100% complete; this section describes guidelines for common system aspects and behavior to be tested

  • Logging
  • Usability
  • Supportability and upgradeability
  • Free (exploratory) testing

Risk Management – QA as Part of Project

Software development is considered very interdependent industry. The section handles main aspects in risk management, in terms of identification, assessment, and mitigation

  • Risk identification and assessment and avoidance planning
  • Risk assessment calculations
  • Risk management planning – documentation, control and tracking, flag raising
  • Outcomes of unsuccessful risk management, examples from practical experience
  • Brooks Law

Advanced Approaches in SQA

The section describes advanced approaches towards software quality assurance, as well as several practical recommendations

  • Cost-effectiveness of QA – when is it worth to find a bug
  • Transition gates – Entry / Exit criteria
  • Adaptations of QA processes to software development model – Agile, XP vs. conservative development models
  • QA group as part of organization, impact of maturity on processes.
  • Pitfalls from practical experience

Test Automation

The section comes to describe the main benefits and disadvantages of automated software testing, as well as common practices for integration of automated testing into organization. Examples given on freeware web testing automation suites

  • Pros and Cons of automated testing
  • Functional testing automation
  • Performance and Stress testing automation
  • Regression vs. Progression - Could a robot replace a man?

Process and Tracking Tools

  • HP Quality Center – Brief Introduction
  • IBM Rational ClearQuest – Brief Introduction

Popular Tools and Important Software

  • SQL – understanding the language, basic queries
  • XML – understanding the basics
  • Debugging principles – symbols, stripped/unstripped code
  • Linux/Unix OS environment – basic commands and system architecture.
  • Sniffers
  • Hardware virtualization environments (VMWare server)
  • Functional Testing suites
Открыта запись на курс. Подробнее здесь:
salvador4k: (Default)
Омлет, обещанный через две минуты, может успешно жариться, но если через две минуты он не готов, то у клиента есть две возможности: ждать еще или съесть его сырым.

Краткое руководство по проджект-менеджменту, Фредерик Брукс, Мифический Человекомесяц
salvador4k: (Default)
Watchdog в треде - как пурген в обеде!
salvador4k: (Default)
Недавно прочитал книгу, от корешка до корешка (к сожалению, дабы не испортить чистоту восприятия, читал перевод)
Много думал

Что же это получается, грабли не исчезают, а всего навсего превращаются в более тяжелую и больную газонокосилку

Решил поделиться несколькими цитатами (увы, на русише). Будет время и желание - кореллирую с оригиналом. Но это уже потом, половину, может быть


salvador4k: (Default)

May 2011

12 34567


RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Sep. 23rd, 2017 12:21 am
Powered by Dreamwidth Studios