ICST: International Conference on Software Testing, Verification, and Validation

FacebookTwitterLinkedInGoogle

 

Past:   Proceedings on DBLP

Future:  Post a CFP for 2020 or later   |   Invite the Organizers Email

 
 

All CFPs on WikiCFP

Event When Where Deadline
ICST 2019 International Conference on Software Testing, Verification, and Validation
Apr 24, 2019 - Apr 26, 2019 Xi'an, China Oct 12, 2018 (Oct 5, 2018)
ICST 2018 The 11th IEEE International Conference on Software Testing, Verification, and Validation (ICST 2018)
Apr 9, 2018 - Apr 13, 2018 Västerås, Sweden Oct 12, 2017 (Oct 5, 2017)
ICST 2017 IEEE International Conference on Software Testing, Verification and Validation (ICST) 2017
Mar 13, 2017 - Mar 18, 2017 Tokyo, Japan Sep 23, 2016
ICST 2016 IEEE International Conference on Software Testing, Verification and Validation (ICST) 2016
Apr 10, 2016 - Apr 15, 2016 Chicago Oct 23, 2015
ICST 2015 IEEE International Conference on Software Testing, Verification and Validation
Apr 13, 2015 - Apr 17, 2015 Graz, Austria Oct 24, 2014
ICST 2014 International Conference on Software Testing, Verification, and Validation
Mar 31, 2014 - Apr 4, 2014 Cleveland, Ohio, USA Sep 23, 2013
ICST 2013 6th IEEE International Conference on Software Testing, Verification, and Validation
Mar 18, 2013 - Mar 22, 2013 Luxembourg Sep 17, 2012
ICST 2013 7th International Conference on Sensing Technology
Dec 3, 2013 - Dec 5, 2013 Wellington, New Zealand Jul 10, 2013
ICST 2012 IEEE Fifth International Conference on Software Testing, Verification and Validation
Apr 18, 2012 - Apr 22, 2012 Montreal, Canada Nov 4, 2011 (Oct 28, 2011)
ICST 2011 International Conference on Software Testing, Validation and Verification
Mar 21, 2011 - Mar 25, 2011 Berlin Oct 1, 2010 (Sep 25, 2010)
ICST 2009 2nd IEEE International Conference on Software Testing, Verification and Validation
Apr 1, 2009 - Apr 4, 2009 Denver, CO, USA Oct 3, 2008 (Sep 26, 2008)
ICST 2008 1st IEEE International Conference on Software Testing, Verification and Validation
Apr 9, 2008 - Apr 11, 2008 Lillehammer, Norway Jan 4, 2008 (Oct 5, 2007)
 
 

Present CFP : 2019

ICST 2019 invites high quality submissions in all areas of software testing, verification, and validation. Papers for the research track should present novel and original work that pushes the state-of-the-art. Case studies and empirical research papers are also welcome.
Topics of interest include, but is not limited to, the following:
● Domain specific testing, such as: mobile or web app testing, embedded systems testing, concurrent systems, GUI testing, etc.
● Formal verification
● Model based testing
● Model checking
● Manual testing practices and techniques
● Search based software testing
● Security testing
● Software reliability
● Test automation
● Testability and design
● Testing and development processes
● Testing education
● Testing in specific domains, such as mobile, web, embedded, concurrent, distributed, cloud, and real-time systems
● Testing/debugging tools
● Theory of software testing
● Empirical studies
● Experience reports
Each submission will be reviewed by at least three members of the ICST Program Committee.
Papers that have a strong industrial/practical component and focus more on impact rather than (technical) novelty are encouraged to consider the industry track instead.
Format
Full Research Papers as well as Industry papers must conform to the two-column IEEE conference publication format. Templates for LaTeX and Microsoft Word are available from http://www.ieee.org/conferences_events/conferences/publishing/templates.html: please use the letter format template and conference option.

Papers should be submitted in the PDF format: they must not exceed ten pages, plus up to two pages of references. Submissions will be handled via EasyChair.

Papers must neither have been previously accepted for publication nor be under submission in another conference or journal. The ICST 2019 research track accepts only full research papers. Short papers are not accepted to the research track.

For your paper to be published in the ICST 2019 conference proceedings, at least one of the authors of the paper must register for the conference and confirm that she/he will present the paper in person.

Submission Site: https://easychair.org/conferences/?conf=icst2019


Important Dates (all dates are AoE)
● October 5th, 2018: Submission of Abstract
● October 12th, 2018: Submission of Full Research Papers
● December 18th, 2018: Author Notification
● Main Conference: April 24-26th (workshops and other events occur before/after these dates)

Double Blind
ICST 2019 is adopting Double Blind Reviewing: research track submissions should not reveal the identity of author(s) in any way; names and affiliations should be left out. Authors should also ensure that citations to their own work are written in third person (i.e. do not write “our previous work”; use “the previous work of X”).

Double Blind Process FAQ

Q: How does one prepare an ICST 2019 submission for double-­blind reviewing?
In order to comply, you do not have to make your identity undiscoverable; the double­-blind aspect of the review process is not an adversarial identity discovery process. Essentially, the guiding principle should be to maximize the number of people who could plausibly be authors, subject to the constraint that no change is made to any technical details of the work. Therefore, you should ensure that the reviewers are able to read and review your paper without having to know who any of the authors are. Specifically, this involves at least the following four points:
1. Omitting all authors’ names, affiliations, emails and related information from the title page as well as in the paper itself.
2. Referring to your own work in the third person. You should not change the names of your own tools, approaches or systems, since this would clearly compromise the review process. It breaks the constraint that “no change is made to any technical details of the work”. However, you should always refer to the authorship/provenance of tools, approaches or systems in the third person, so that it is credible that another author could have written your paper.
3. Not relying on supplementary material (your web site, GitHub repository, YouTube channel) in the paper. Supplementary information might result in revealing author identities.
4. Anonymize project and grant names and numbers or those of funding agencies or countries as well as any acknowledgements of support to the work you report on.
We further expect you to follow the excellent advice on anonymization from ACM: https://icer.hosting.acm.org/icer-2017/additional-advice-on-anonymization/
When anonymizing your email, affiliations, name etc. try to refrain from being overly creative or “funny” by coming up with your own, anonymized versions. For emails preferably use author1@anon.org, author2@anon.org, etc. since initial DBR screening will be done by an automated tool.

Q: I previously published an earlier version of this work in a venue that doesn’t have double-blind. What should I do about acknowledging that previous work?
Double-blind does not and cannot mean that it’s impossible for the referees to discover the identity of the author. However, we require authors to help make it easy for author identity to not play a role in the reviewing process. Therefore, we ask that in the materials you submit to us to be reviewed author identity is not revealed.
If the work you are submitting for review has previously been published in a non-peer-reviewed venue (e.g., arXiv departmental tech report), there is no need to cite it, because unrefereed work is not truly part of the scientific literature. If the previous work is published in a peer-reviewed venue, then it should be cited, but in the third person so that it is not clear whether or not this work was done by the author of the submitted paper or some other set of authors unknown. However, if citing in the third person would still risk that it is easy to identify the authors please err on the side of caution by also anonymising the papers being extended (both when cited and in the reference list).

Q: Our submission makes use of work from a PhD/master’s thesis dissertation/report which has been published. Citing the dissertation might compromise anonymity. What should we do?
It’s perfectly OK to publish work from a PhD/master’s thesis, and there’s no need to cite it in the version submitted for review because prior dissertation publication does not compromise novelty. In the final (post-review, camera ready) version of the paper, please do cite the dissertation to acknowledge its contribution, but in the refereed version of the paper that you submit, please refrain from citing the dissertation.
However, you need not worry whether or not the dissertation has appeared, since your job is only to help the committee review your work without awareness of author identity, but not to make it impossible for them to discover the identity of authors. The referees will be trying hard not to discover the authors’ identity, so they will likely not be searching the web to check whether there is a dissertation related to this work.

Q: I’m submitting to the industry track. Should i double-blind my submission?
No you should not. Since industry papers typically relies heavily on the industrial/practical context in which the work was carried out it would be too much to ask to require this context to be anonymized.

Q: I want to include a link to an online appendix in my submission. How should I do this?
Ideally the information in the appendix should be anonymous and it should be uploaded to an anonymous service such as for example figshare or create a new github (or other) sharing account that is not associated with your real name. These sites will give you a link that is anonymous. Later, if the paper is accepted you can turn that link into a non-anonymized link or just put the appendix on your own site and change the link in the camera ready version of the paper. An alternative solution is to not include the link in the submission; normally papers should be possible to review based on only the material of the paper itself.

To upload material on figshare please create an account there, then add a new item, use the keywords “Supplemental Materials” and add the other item-specific data and then select “Make file(s) confidential” and select “Generate private link”. Copy the url generated there and then “Save changes”. Your file(s) can now be accessed anonymously at the given url so you can put it in your ICST submission.
 

Related Resources

ICST 2018   The 11th IEEE International Conference on Software Testing, Verification, and Validation (ICST 2018)
ITEQS 2019   3nd International Workshop on Testing Extra-Functional Properties and Quality Characteristics of Software Systems
ISSTA 2019   International Symposium on Software Testing and Analysis
QRS 2019   The 19th IEEE International Conference on Software Quality, Reliability, and Security
RQD 2019   25th ISSAT International Conference on Reliability and Quality in Design
TOOLS 2019   Technology of Object-Oriented Languages and Systems
HCVS 2019   6th Workshop on Horn Clauses for Verification and Synthesis
FVPS 2018   Formal Verification of Physical Systems
ADON 2018   International Workshop on Anomaly Detection ON the Cloud and the Internet of Things
MVV 2018   IEEE International Workshop on Model-Based Verification & Validation