0% found this document useful (0 votes)
4 views6 pages

Software Testing Course Syllabus 2023

This syllabus describes a Software Testing course worth 2 credits and 3 hours per week. The course focuses on best practices and tools for software testing to provide knowledge on how to determine if the software is ready for release. The course consists of 4 learning units on test management, unit and functional testing, performance and security testing, and testing for mobile devices. Students will be evaluated on
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views6 pages

Software Testing Course Syllabus 2023

This syllabus describes a Software Testing course worth 2 credits and 3 hours per week. The course focuses on best practices and tools for software testing to provide knowledge on how to determine if the software is ready for release. The course consists of 4 learning units on test management, unit and functional testing, performance and security testing, and testing for mobile devices. Students will be evaluated on
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

SYLLABUS

Software testing (100000S13F)


2023 - Cycle 1 March

1. GENERAL DATA

[Link]: Software Engineering

1.2. Credits: 2

1.3. Course teaching: In-person

1.4. Weekly hours: 3

2. FOUNDATION
The subject presents an overview of the best practices and tools for testing software.
to the present, providing the student with solid knowledge regarding software testing, the
the same that are important for your training as an engineer, as it provides the necessary knowledge to
determine whether the software is ready to proceed or not, based on the test results
that were carried out.

3. SUMMARY
The subject is of a theoretical-practical nature and presents fundamental concepts and provides the skills
techniques through the application of tools to be used for the daily tasks of a test engineer
software. It deals with topics related to unit testing, functional testing, performance testing,
security testing and agile testing in different types of software according to their type of environment and/or device
where they operate: desktop, standalone, legacy, core, web, distributed, and mobile.

4. GENERAL LEARNING ACHIEVEMENT


Upon completing the course, the student designs test cases using appropriate technological tools.
various types of applications.

5. UNITS AND SPECIFIC LEARNING ACHIEVEMENTS

Learning Unit 1: Week 1, 2, 3, and 4


Management and Traceability of Test Cases.

Specific learning achievement:


The student completes a full cycle of creating test plans, creating specifications, creating
test cases, execution of test cases and detection of software defects, and follow up on
the defects until their respective solution.

Syllabus:
Software Testing Projects. Qualities of a good software tester. Requirements engineering
oriented towards software testing. ISO 9126, SWEBOK, and ISTQB. The planning of Testing Projects
Software. The processes of a software testing project.
Methodologies, Types, and Techniques of Software Testing. Principles of software testing. Methodologies of
Software Testing. Types of software testing: black box testing, white box testing, and testing
of gray box.
Software Verification and Validation. Software verification. Differences between verification and validation.
software. Software quality assurance. Software certification software quality control.
Software Testing Strategies. Effective software testing strategies.

Learning Unit 2: Week 5, 6, 7, 8, 9, and 10


Unit, Functional, and Integral Tests.
Specific learning achievement:
Al finalizar la segunda unidad, el estudiante diseña casos de pruebas para probar componentes de software a un
specific software functional level. He also knows the proper way to test software in methodologies of
agile software development and traditional software development methodologies.

Syllabus:
Unit Testing and Agile Testing. The way of working in Agile Testing. Introduction to Jenkins and others.
tools for Agile Testing.
Effective Unit Test Design. Effective writing of test cases. TDD: Test Driven Development.
Functional Testing with Selenium. Creation of Functional Tests. Execution of Functional Tests.
Functional Testing with Sikuli(1). Introduction to Creating Functional Tests with Sikuli.
Functional Testing with Sikuli(2). Creation of Basic Functional Tests. Execution of Functional Tests.
Comprehensive Web Service Testing with SOAPUI. Creation of Complex Functional Tests Execution of
Functional Tests

Learning Unit 3: Week 11, 12, 13 and 14


Performance Testing and Security Testing.

Specific learning objective:


At the end of the third unit, the student designs and is able to use tools to conduct tests.
performance, stress and load. Likewise, the student tests the security of different web applications and
mobile applications.

Syllabus:
Pruebas de Rendimiento (1). Introducción a las Pruebas de Rendimiento. Tipos de Pruebas de Rendimiento:
Performance, Stress y Carga. Concurrencia, Latencia y throughput.
Performance Testing (2). Open source tools for performance, stress, and load testing (Badboy,
JMeter).
Security Testing (1) Security Testing based on OWASP Top 10. Security Testing using the
W3AF tool.
Security Tests (2). Security tests using the Acunetix tool.

Learning Unit 4: Week 15, 16, 17, and 18


Software testing on mobile devices.

Specific learning achievement:


At the end of the fourth unit, the student designs and is able to use tools to carry out tests to
software on mobile devices.

Syllabus:
Software testing on mobile devices (1). Analysis of external communications of the application. Analysis
of file, memory, and network management.
Software testing on mobile devices (2). Study of the protection structure of storage
data.
Applications of real cases.
FINAL EXAM.

6. METHODOLOGY
Individual and team work. Practical cases of the topics covered in class. The topics will be addressed with
practical team monographic works. Use of Multimedia and laboratories. The class sessions will be
complemented with support from digital resources uploaded on the virtual platform.

7. EVALUATION SYSTEM
The calculation of the final average will be done as follows:

(20%)PC1 + (20%)PC2 + (30%)PC3 + (30%)EXFI

Where:

Type Description Week Observation

PC1 QUALIFIED PRACTICE 1 5 graded practice 1

PC2 QUALIFIED PRACTICE 2 10 qualified practice 2


Type Description Week Observation

PC3 QUALIFYING PRACTICE 3 15 graded practice 3

EXFI FINAL INDIVIDUAL EXAM 18 individual final exam

Guidelines on Evaluation Formulas:

The minimum passing grade is 12.

2. The student who does not take the final exam can take a single makeup exam. The grade obtained in
this makeup exam replaces the final exam not taken.
The student takes the make-up exam on the date scheduled by the University, after presentation
of request and payment of the fees for the postponed exam set forth in the current rate schedule and published
in Student Portal. The makeup exams are held at the end of the academic period and cover all
the topics covered in the subject.

3. In case a student does not take a graded practical exam (PC) and therefore receives NSP, this is
replaced by the grade obtained in the final exam. If you also have NSP in the final exam, this is
replaced by the grade obtained in the makeup exam. This grade replacement is automatic. It is not
it is necessary for the student to carry out any procedure for the replacement of the grade to take place. In case that
if the student has more than one unfulfilled graded practice, only the graded practice of
greater weight.

Only one Qualified Practice or the Final Exam can be deferred (not both).

The delayed exam includes the contents of the entire course.

6. No graded practice is removed.

7. In the case that a student does not complete a graded practical (GP) and therefore receives a NS, this is
replaced with the grade obtained in the final or makeup exam. In case the student
If you have more than one unsubmitted graded assignment, only the graded assignment with the highest weight will be replaced.

8. It is not necessary for the student to carry out any procedure for this replacement to take place.

8. SOURCES OF INFORMATION
Basic Bibliography:
Joyanes, [Link]ÓN EN LA NUBE - ESTRATEGIAS DE CLOUD COMPUTING EN LAS EMPRESAS.
Alfaomega . [Link]
Supplementary Bibliography:
Monsalve Sossa, Doris [Link] a aplicaciones móviles: avances y retos. Lámpsakos, (21), 39-
[Link] Amigó Catholic University. [Link]
biblionumber=37723
Ollero Sánchez, Carlos - Author. Testing functionalities and optimization of web pages (UF1306).
IC Editorial.
Raya Cabrera, José Luis - Author; Raya González, Laura - Author. Installation and configuration of systems
operational. Editorial CEP, S.L. [Link]
biblionumber=36972
Ollero Sánchez, Carlos - Author. Student's notebook: functionality tests and optimization of
web pages (UF1306). Fabrication and publication of Web pages (IFCD0110). Editorial CEP, S.L.
[Link]
Miguel Aristizábal - Author; Echeverri, Jaime - Author; Liliana González - Author. Reflections on
requirements engineering y software testing. Remington University Corporation.
The requested page could not be translated as it is a link and contains no translatable content.

9. SKILLS

Race Specific competencies

Software Engineering Systems Analysis


Software Development

[Link] SCHEDULE
Activities and
Learning unit Semana Sesión Tema
evaluations

Software Testing Projects.


Entry test.
Qualities of a good tester
Create projects of
software. The engineering of
tests in Testlink
test-oriented requirements
of the software. ISO 9126, SWEBOK and
Creation of Plans
1 1 of Tests in
ISTQB. Project Planning
Testlink Creation
Software Testing. The processes of a
Specifications
Software testing project.
from Software to
Testlink testing.

Methodologies, Types, and Techniques of


Create cases of
Software Testing. Principles of
tests in
software testing. Methodologies of
Testlink. Execution
Software Testing. Types of testing
Test Cases
software: black box testing,
in Testlink.
white box testing and testing of
Identification of
2 2 gray box.
Defects of
software with
Unit 1 Testlink.
Administration and Generation of
Case Traceability of Reports of
Tests. Tests in Testlink.

Software Verification and Validation. The


Register defects
software verification. Differences
of the software in
between verification and validation of
Mantis Web.
software. Quality assurance
Follow-up until
software. Software certification
the closing of
software quality control.
3 3 Defects in Mantis
Web. Registration of
Defects and
Follow-up of
Defects in
MantisDroid.

Software Testing Strategies.


Reconocer
effective testing strategies of
strategies
4 4 software.
effective of
testing.

Unit Tests and Agile Testing. The


Unit Tests
Agile testing work format.
using Netbeans and
Introduction to Jenkins and other tools
JUnit for testing
for Agile Testing.
Java applications
standalone y
5 5 creation of Jobs in
Jenkins for
Integration
Continue.
PRACTICE
QUALIFIED 1

Effective Unit Test Design.


Unit Tests
Effective writing of test cases.
using Netbeans and
TDD: Test Driven Development.
6 6 JUnit for testing
Java applications
Web.

Unit 2 Functional Testing with Selenium.


Unit Tests Conduct tests
Creation of Functional Tests.
Functional and Integral. 7 7 functional with
Execution of Functional Tests. Selenium.

Functional Testing with Sikuli(1).


To know how
Introduction to Test Creation
create tests
8 8 Functional with Sikuli.
basic functionalities
with Sikuli.

Functional Tests with Sikuli(2).


Create tests
Creation of Functional Tests
9 9 basic functionalities
Basics. Test Execution
with Sikuli.
Functional.

Integral Testing of Web Services with


Functional tests
SOAPUI. Test Creation
complex with
Complex Functionals Execution of
10 10 Sikuli.
Functional Tests
PRACTICE
QUALIFIED 2

Performance Tests (1).


Identify tests
Introduction to Testing
of performance.
Performance. Types of Tests
11 11 Performance: Performance, Stress and
Load. Concurrency, Latency and
throughput.

Performance Tests (2).


Tests of
Open source tools for testing
performance
of performance, stress, and load (Badboy,
using the
JMeter).
12 12 tools
JMeter, Badboy and
Unit 3 other tools
Performance Tests online.
and Security Tests.
Security Tests (1) Testing of
Conduct tests of
Security based on OWASP Top 10.
security based
Security Tests using the
13 13 in OWASP Top 10.
W3AF tool.
and the tool
W3AF

Security Tests (2). Tests of


Conduct test of
Security using the tool
safety
Acunetix.
14 14 using the
tool
Acunetix.

Software testing on devices


Pruebas a software
mobile phones (1). Communication analysis
external aspects of the application. Analysis of for devices
mobile with
file management, memory and network.
tools
online: Browser
15 15
Stack and others
tools
Online.
PRACTICE
QUALIFIED 3

Unit 4 Software testing on devices


Software testing in Software testing
mobiles (2). Study of the structure of
Mobile Devices. for devices
storage protection
16 16 mobiles with
data.
Robotium and
Appium.
Real case applications. Various tests in
17 17 real cases.

FINAL EXAM.
FINAL EXAM
18 18
INDIVIDUAL

You might also like