forked from sbft24/sbft24.github.io
-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathindex.html
More file actions
111 lines (101 loc) · 6.97 KB
/
Copy pathindex.html
File metadata and controls
111 lines (101 loc) · 6.97 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
---
title: SBFT'25 Homepage
layout: default
---
<div class="col-md-8 text-justify">
<h4 class="subsection">About SBFT</h4>
<p>Optimization techniques can be
applied to many aspects of the software development process:
research areas known as Search-Based Software Engineering
(SBSE).
In our previous workshop editions, we focused on the application of SBSE to perform testing tasks, the so called
Search-Based Software Testing (SBST).
Ongoing research on SBST and Fuzz Testing are proposing techniques to address similar testing problems and with
similar goals.
This has led to the decision to rename the workshop to <b>Search-Based and Fuzz Testing (SBFT)</b>.
SBFT strategies have been applied to a wide variety of testing goals
including achieving high coverage, finding faults and vulnerabilities, and
checking various state-based and non-functional properties (e.g., scalability, acceptance).
</p>
<p>
The central objective of this workshop is to bring together researchers
and industrial practitioners from SBST, Fuzzing, and the wider Software
Engineering community to share experience and provide directions for
future research on the automation of software testing.
The second objective of this workshop is to encourage the use of search and fuzzing techniques to
combine testing with other software engineering areas.
SBFT is a two-day workshop that comprises a research track, keynotes, and popular
testing tool competitions. Additionally, the workshop brings together experts for a panel discussion.
All those activities will contribute to break new ground in SBFT research.</p>
<h4 class="subsection">Attending SBFT</h4>
<p>
SBFT 2025 is co-located with <a href="https://conf.researchr.org/home/icse-2025" target="_blank">ICSE 2025</a>.
<br>
In order to attend SBFT, you have to register for our workshop using the official <a
href="https://conf.researchr.org/attending/icse-2025/registration" target="_blank">ICSE
registration link</a>.
<br>
Once you registered for SBFT, the ICSE team will send you an e-mail with the invitation to attend
the conference.
</p>
<p class="paper-title">
<b>Similar to last year, we will also live-stream SBFT 2025 via Twitch. Feel free to join our stream and ask questions in the chat if you are not registered.
</p>
<h4 class="subsection">Call for Papers</h4>
<p>Researchers and practitioners are invited to submit:</p>
<ul>
<li>Full papers (maximum of 8 pages, including references): Original research in SBFT, either empirical, theoretical,
or practical experience using SBFT techniques. Since this edition, we also welcome research on challenges, innovations,
and best practices in software quality assurance education with/for SBFT.</li>
<li>Short papers (maximum of 4 pages, including references): Work that describes novel techniques, ideas,
and positions that have yet to be fully developed or are a discussion of the importance of a recently published
SBFT result by another author in setting a direction for the SBFT community, and/or the potential applicability (or not) of the result in an industrial context.</li>
<li>Demonstrations papers (maximum of 4 pages, including references): Work that describes novel aspects of early
prototypes or mature tools and communicates tools' envisioned users, the addressed SBFT challenges, and achieved results.
Authors of regular research papers and tool competition participants are encouraged to submit an accompanying demonstration paper,
ensuring that tool details are not discussed in the original paper.</li>
<li>Position papers (maximum of 2 pages, including references): Work that analyzes SBFT trends and raises important issues.
Position papers are intended to seed discussion and propose new ideas; thus, they will be reviewed with respect to relevance and potential ability to spark discussions.</li>
<li>Tool competition entries: We invite researchers, students, and tool developers to design innovative new approaches to software test generation.
SBFT 2025 will host four testing tool competitions: unit testing of Java, CPS testing of self-driving cars and unmanned aerial vehicles, and fuzz testing.</li>
</ul>
<p>In all cases, papers should address a problem in the software testing/verification/validation
domain or combine elements of those domains with other concerns in the software engineering
lifecycle. Examples of problems in the software testing/verification/validation domain include (but
are not limited to) generating testing data, fuzzing, prioritizing test cases, constructing test
oracles, minimizing test suites, verifying software models, testing service-orientated
architectures, constructing test suites for interaction testing, SBFT for AI applications, machine
learning techniques for SBFT, and validating realtime properties.</p>
<p>The solution should apply any kind of fuzzing or a metaheuristic search strategy such as (but not limited to)
random
search, local search (e.g. hill climbing, simulated annealing, and tabu search), evolutionary
algorithms (e.g. genetic algorithms, evolution strategies, and genetic programming), ant colony
optimization, particle swarm optimization, and multi-objective optimization.</p>
<h4 class="subsection">Special Issue</h4>
<p>
This topic is currently under discussion. More information coming soon!
</p>
<p>Photo by Timothy Lethbridge, licensed under <a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank">CC BY-NC 4.0</a>.</p>
<a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank">
<img src="/img/by-nc.svg" alt="CC BY-NC License">
</a>
<span style="float: right; vertical-align: top;">
<img height="24px" style="vertical-align:top" src="https://conf.researchr.org/getLogo/5d74ba38-698f-46af-9929-3dc0700e6142?1698376867000" alt="TCSE logo">
<br>
<img height="24px" style="vertical-align:top" src="https://conf.researchr.org/getLogo/673e6c15-1ebb-413d-80e6-00c17a7a120a?1698376919000" alt="Sigsoft logo">
</span>
<!-- <h4 class="subsection">Sponsors</h4>
<div class="sponsors">
<a href="https://ledcity.io/en/" target="_blank"><img src="/img/ledcity.jpg" alt="LEDCity" class="img-fluid"
width="170" /></a>
<a href="https://www.beamng.com/game/" target="_blank"><img src="/img/beamng.png" alt="BeamNG" class="img-fluid"
width="600" /></a>
<a href="https://www.google.com/" target="_blank"><img src="/img/google.png" alt="Google" class="img-fluid"
width="230" /></a>
<a href="https://tc.computer.org/tcse/" target="_blank"><img src="/img/tcse.jpg" alt="IEEE TCSE" class="img-fluid"
width="230" /></a>
<a href="https://www.sigsoft.org/index.html" target="_blank"><img src="/img/sigsoft.png" alt="ACM SIGSOFT"
class="img-fluid" width="230" /></a>
</div> -->
</div>
{%- include sidebar.html -%}