learnsoftwaretesting

  Java Java Enterprise Edition (2020) Not required Servlet RESTFull Logging Servlet RESTFull Logging Including all requirements from previous proficiency scales. Persistence API Java Message Service Common Annotations Hibernate Including all requirements from previous proficiency scales. Persistence API Java Message Service Common Annotations Hibernate Including all requirements from previous proficiency scales. Enterprise Java Beans Java Standard Edition (2020) core competency Not required Core (Lang) Collections Framework Functional Interfaces Stream API IO Including all requirements from previous proficiency scales. Multithreading Java 8+ Features: forEach() method in Iterable interface default and static methods in Interfaces Functional Interfaces and Lambda Expressions Java Stream API for Bulk Data Operations on Collections Java Time API etc. Including all requirements from previous proficiency scales. NIO Reflection API Including all requirements from pr...

  Software Testing Test design (2020) core competency Not required Designs simple functional test cases and checklists for individual features. Some of test cases may be incomplete and inaccurate. Has general understanding of test design techniques. Including all requirements from previous proficiency scale. Designs test cases and checklists for entire application components and majority of testing types. May miss some non obvious test cases or test case elements. Applies mainly specification-based test design techniques (e.g. decision table, state transition, boundary value analysis, equivalence partitioning). Predicts test case execution time (although may be with low level of precision), defines obvious environment and configuration-specific cases. Possesses at least basic expertise with test management tools. Including all requirements from previous proficiency scale. Designs test cases and checklists for entire application components and majority of testing types. May m...

  Golang Concurrency (2020) core competency Not required Not required Knows what is goroutine and how to create it. Knows what are channels and types of channels. Can create a channel, write and read from it. Knows what is "select" and how use it. Knows about order of cases in "select". Knows how to close a channel and detect closing. Knows how to use time.Sleep(). Knows what race conditions are. Knows how to work with sync.Mutex, sync.RWMutex, sync.WaitGroup, sync.Once. Including all requirements from previous proficiency scales. Knows what is goroutine context switching and when it happens. Knows goroutine leak and how detect it. Knows what will be if we will try to write and read from a closed and nil channels. Knows how to validate channel direction. Know how to work with atomic functions. Know how to use GOMAXPROCS. Knows how to work with time.Ticker() and why we have to close it. Knows how to work with time.Timer() and time.AfterFunc(). Can stop or r...

Standards can be defined as a set of obligatory requirements established by a general agreement and maintained by a recognized body to impose a uniform disciplined practice. Standards provide mutually agreed guidelines and instructions to people and organizations with a basis for mutual comprehension and are used as tools to facilitate measurement. We have five standards within the ISO/IEC 29119 international software testing standard: • ISO/IEC 29119-1: This was published in Sep 2013 and deals with concepts and definitions of software. • ISO/IEC 29119-2: This Standard deals with test processes in a product and was published in Sep 2013. • ISO/IEC 29119-3: This was published in Sep 2013 and deals with test documentation of the product. • ISO/IEC 29119-4: This Standard was published one year later in 2014 and deals with testing techniques and strategies used in software testing. • ISO/IEC 29119-5: This Standard was published in the year 2015 and deals with keyword-based s...

The Fault is a state that causes the software to fail to accomplish its essential function. If the software has lots of defects, it leads to failure or causes failure . Raised by. The Test Engineers submit the bug. Software fault is a static defect in the software. The fault is always a developer (human) software design mistake. Software failure is product external unexpected behavior concerning expected behavior (listed in requirements or common sense behavior). ... During development Failures are usually observed by testers. FAULT: An incorrect step, process or data definition in a computer program which causes the program to perform in an unintended or unanticipated manner. A fault is introduced into the software as the result of an error. ... It is the result of the error.