COMMAND

dir - to list folders and files

cd - to change directory
cd .. - to move to the parent folder of the current folder
cd \  - to move to the root folder
cls - to clear the current screen
md - to create a folder in the current location (root drive, folder)
Up & down keys - to recall previous commands
Function F3 - to recall the last command you types
Ren - to rename file
move - to rename folder / to move files& folder to a new location
Ctrl+C - to save a batch of files

-- create a batch file (file with the extension .bat) --

rd - to remove a folder  use "/s" to delete folder and files togather
copy - to copy files

 -- Network Related DOS Commands --

ipconfig - to display your network configuration
ping   - to check network status (server status, service status) 
tracert - to check network connections

--Create a dos batch file that will complete the following tasks:
  1. create a folder named test2
  2. enter into the folder test2
  3. create a folder test2-2
  4. enter into the folder test2-2

  Note: at the last line, you press Ctrl+C key to save the batch file
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
framework that defines the steps involved in the development of software at each phase.

Purpose: To deliver high-quality product or Application or software based on the requirements

e.g: Customer

Phases:
Planning
Analysis
Designs
Construction
Testing Cycle
Final Testing
Post Implementation

Software Development Life Cycle Models

#1) Waterfall Model
#2) V-Shaped Model
#3) Prototype Model
#4) Spiral Model
#5) Iterative Incremental Model 
#6) Big Bang Model
#7) Agile Model

What is QA function in SDLC process?

A crucial process that must be implemented during the software development life cycle.
The primary purpose of QA is to ensure that the software meets planned functionality, bug-free,
and it will be working flawlessly under different circumstances.

QA is integrated into all development stages, and it is used even after the post-release stage. QA
specialists create and implement various strategies for software quality improvement. They apply
the required testing types to ensure that the software will function correctly — this stage is called
quality control (QC).

Responsibility of QA Team
1. Test planning
 QA analysts plan the testing process, what testing objectives must be met, and what approach is recommended to u
2. Early testing. 
QA engineers conduct early testing to detect bugs during the first development phase and speed up the developmen
3. Test execution.
QA engineers perform manual/automated testing using different types of testing according to the software particula
4. Defects analysis. 
It is necessary to analyze all defects and identify the reason for their occurrence. 
5. Reporting. 
Specialists use bug tracking systems to create reports for developers with descriptions of bugs and defects to be fixe
6. Collaboration. 
The QA team collaborates with business analysts, project managers, developers, and clients to achieve the highest q
7. Test summary report creation. 
When software is tested, QA engineers need to create a test summary report that shows the quality level of software

What Is The Role Of QA In Project Development?

Quality assurance plays a crucial role in every stage of the software development life cycle. Cadabra Studio
does its best to identify all defects and loopholes during software development, and we want to show it is
performed in each stage.

Requirement analysis. 

QA team collaborates with business analysts to perform a feasibility study of requirements, analyze
possible risks, create test plans, build a strategy for a testing approach (each project requires an
individual approach due to its uniqueness), what testing types will be used, etc.

Design. 

It is necessary to review the design, verify its testability, check whether the design architecture meets
all functional and non-functional requirements. Also, QA specialists make Data Flow Diagram (DFD)
together with UI/UX designers and document it. Finally, QA engineers test the design after its
completion to imitate end-user behavior. 

Development. 

The software development testing may be performed once the software is created, or it is possible to
use the TDD approach — test-driven development. TDD means that the software undergoes a testing
process during the development, after each iteration. At Cadabra Studio, we apply both methods
depending on software particularities and the client’s demands. 

Post-release QA. 

Once the product is released, developers keep on maintaining it, and the QA team creates user guides
and manuals of the product to deliver it to the end-user. Also, specialists draw up testing
documentation to ensure that all bugs have been detected and everything is fixed. 
 Question: as a QA, what is your involvement in each phase of the SDLC process?
Planning (project manager, business analyst, QA Manager ) - Test Plan (LOE - Level
Requirement - (developer, qa team) - test cases (User acceptance criteria)
Design (developer, qa team) - revise (update) test cases, preparing test data
Testing (qa team) (feature level manual testing, automated regression testing, pe
deployment(DevOps, QA team) final production smoke test (sanity testing, ad hoc
Maintenance (Product) (software upgrade, OS system upgrade) - smoke test, sanity

ach is recommended to use.

peed up the development process.

to the software particularities.

ugs and defects to be fixed.

to achieve the highest quality of a software product.

e quality level of software.
 ) - Test Plan (LOE - Level of Effort)
eptance criteria)
preparing test data
ted regression testing, performance testing)
st (sanity testing, ad hoc testing)
rade) - smoke test, sanity check, ad hoc test
SOFTWARE TESTING LIFE CYCLE
TYPES OF SOFTWARE TESTING

1 Functional Testing : implies the testing of functional software aspects. Functional testing types show the internal behavio

Type of Funtional Testing:

1. Unit testing : The testing of an individual unit or group of related units.
2. Integration testing
3. End-to-end testing
4. System testing
5. Smoke testing : The test team will navigate through the main application functionality to ensure build stability and t
6. Sanity testing
7. Acceptance testing : The testing is often done by the customer to ensure that the delivered product meets the requ
8. Regression testing : The testing after modification of a system, component, or a group of related units to ensure th
9. White box and black box testing
10. Interface testing

Functional testing can be performed both manually (so QA engineers do everything manually step by step)
and with the help of automated testing (relevant software conducts the testing of your software, and then
the QA engineer gets a result).

2 Non-Functional Testing : implies testing of how the system works, how non-functional aspects of the software like perform

Type of Non-Funtional Testing:

1. Performance testing : The testing to assess the speed and effectiveness of the system and to make sure it is gener
2. Security testing
3. Load testing
4. Reliability testing
5. Usability testing
6. Scalability testing
7. Compatibility testing
8. Volume testing
9. Stress testing
10. Maintainability testing
11. Compliance testing
12. Efficiency testing, etc. 

Non-functional testing helps QA engineers improve your software to a great extent, and it is always a
second step after the non-functional testing, but vital nonetheless. And it is always performed using
automation tools since it is a rather complicated process, and manual tests will take too much time and
effort. 

3 Unit Testing : Validating that each software unit performs as expected. A unit is the smallest testable component of an ap
4 System Testing
5 Integration Testing : Ensuring that software components or functions operate together.
6 End to End Testing
7 Acceptance Testing : Verifying whether the whole system works as intended.
8 Smoke Testing
9 Security Testing
10 Sanity Testing
11 Performance Testing : Testing how the software performs under different workloads. Load testing, for example, is used to
12 Regression Testing : Checking whether new features break or degrade functionality. Sanity testing can be used to verify m
13 Alpha Testing
14 Beta Testing
15 Black Box Testing
16 White Box Testing
17 Stress Testing : Testing how much strain the system can take before it fails. Considered to be a type of non-functional tes
how the internal behavior of the software, how it may interact with other systems.

nsure build stability and to accept the build for additional system testing efforts.

d product meets the requirements and works as the customer expected.

related units to ensure that the modification is working correctly and is not damaging or imposing other modules to produce unexpected res

f the software like performance, usability, security, etc., show themselves.

d to make sure it is generating results within a specified time as in performance requirements.

able component of an application.

ng, for example, is used to evaluate performance under real-life load conditions.
ng can be used to verify menus, functions and commands at the surface level, when there is no time for a full regression test.

ype of non-functional testing.

o produce unexpected results.

ression test.
CSS SELECTOR PSEUDO-CLASSES
is a keyword added to a selctor that specifies a special state of the selected webelement (hyrarcy code)

1. First-child - returns first element from the group of sibling elements.

parent#id>;first-child/parent#id ;first-child
2. Last-child - returns last element from the group of sibling elements.
parent#id>;last-child/parent#id ;last-child
3. nth-child() - return elements based on their position in a group of siblings.
parent#id tag;nth-child(n) / parent#id *;nth-child(n)
4. nth-last-child() - return elements based on their position among a group of siblings, counting from the end.
parent#id tag;nth-last-child(n) / parent#id *;nth-last-child(n)

CSS : Cascading Style Sheet

 incorrecterror
When tester finds a mistake or problem then it is referred to as Defect.
Once a defect found by a tester is accepted by developer it is called a bug.
Defect
Answer 3
Bug
Incident is an unplanned interruption.
Answer 4
Incident
The set of generic and specific conditions, agreed upon with the stakeholders for permitting a process to be officially co
Answer 5
Exit Criteria
The test closure phase consists of finalizing and archiving the test ware and evaluating the test process, including prepa
Answer 6
Test Closure
The process of running a test on the component or system under test, producing actual result(s).
Answer 7
Test Execution
The process of developing and prioritizing test procedures, creating test data and, optionally, preparing test harnesses
Answer 8
Test Implementation
The activity of establishing or updating a test plan.
Answer 9
Test Planning
The fundamental test process comprises test planning and control, test analysis and design, test implementation and e
Answer 10
Test Process
Commonly used to refer to a test procedure specification, especially an automated one.
Answer 11
Test Script
Software Test Life Cycle
Answer 12
STLC
Software Development Life Cycle
Answer 13
SDLC
Planning, Analysis, Designs, Construction, Testing Cycle, Final Testing, Post Implementation
Answer 14
STLC Phases
Concept Initiation, Requirement Analysis, Design, Implementation, Unit Test, Integration Test, System Test
Answer 15
SDLC V-Model

This is to verify that application under test users can access only those functions/data for which their user type is provided per
Answer 1
Role Based Security Testing
The testing which is done by end users, a team outside development, or publicly releasing full pre-version of the product whic
Answer 2
Beta Testing
The testing to evaluate how system behaves under unfavorable conditions.
Answer 3
Stress Testing
The testing to ensure that by putting the software in different environments (e.g., Operating Systems) it still works.
Answer 4
System Testing
The testing is performed to the perspective of the client about the usability of the application. 
Answer 5
Usability Testing
Section 508 Compliance Testing ensures that the software meets 508 Compliance requirements.
Answer 6
508 Compliance Testing
The Testing in which a group of components are combined to produce output.
Answer 7
Integration Testing
The testing to assess the speed and effectiveness of the system and to make sure it is generating results within a specified tim
Answer 8
Performance Testing
The test team will navigate through the main application functionality to ensure build stability and to accept the build for addi

Answer 9
Smoke Testing
The testing is often done by the customer to ensure that the delivered product meets the requirements and works as the cust
Answer 10
Acceptance Testing
The test to ensure that the specified functionality required in the system requirements works
Answer 11
Functional Testing
Test web application on different browsers to make sure that the application runs smoothly on various browsers such as Firefo

Answer 12
Browser Compatibility Testing
The testing after modification of a system, component, or a group of related units to ensure that the modification is working c
Answer 13
Regression Testing
The testing of an individual unit or group of related units.
Answer 14
Unit Testing
tting a process to be officially completed.

e test process, including preparation of a test evaluation report

ally, preparing test harnesses and writing automated test scripts.

gn, test implementation and execution, evaluating exit criteria and reporting, and test closure activities.

Test, System Test

their user type is provided permissions based on the functional and design documentations.
e-version of the product which is known as beta version.

tems) it still works.

g results within a specified time as in performance requirements.

nd to accept the build for additional system testing efforts.

ements and works as the customer expected.

various browsers such as Firefox, chrome, IE, Safari and other browsers.

t the modification is working correctly and is not damaging or imposing other modules to produce unexpected results.
pom xml
penulisan besar dan kecil