Strategies, Techniques, Tools and Best Practices for QA and Test in Continuous Integration, Delivery and Deployment
Software and IT-based systems are to be developed within an ever shorter periodof time at lowest possible costs and with high quality. For this purpose, the QA and tests of the systems will have to be automated throughout the entire process, from the tool-supported administration and verification of requirements, through completely automated statistic and dynamic tests to automatic deployment into the target environment.
In order to master these challenges successfully, strategies, techniques, tools and best practices for test and quality assurance will be presented and discussed at the Software-QS-Tag 2018.
Invitation for the submission of conference contributions, tutorials and workshop proposals
We are looking forward to your field reports, tutorials, workshops and new practice-related research results from application areas such as: Company IT, e-Commerce, Digital Services, Digital Media, Internet of Things, Embedded Systems, Mobile Devices, Robotics, Autonomous Systems, Safety Critical Systems (such as Healthcare, Automotive, Rail) etc.
The contributions will be presented in five tracks running parallel on two conference days.
Your contribution will have to match one of these tracks. For example, by entering into one or more of the following issues:
- Requirements & (agile) Scaling
How are requirements identified, formulated and documented? As discussed and coordinated with the client and within the team? Which methods, notations (User Stories, FDD etc.) and tools are used here? How is testability and traceability of the requirements ensured? How are the non-functional requirements, e.g. related to the system architecture (modularity, reusability, analyzability, test interfaces etc.), dealt with? How does (in larger projects) coordination and synchronization of requirements between different teams, departments and company units involved take shape? How and when do frameworks support agile scaling like SAFe or Nexus™?
- Test management
How is the testing process designed (agile, hybrid, V model etc.) and how is it organized and controlled? Which tasks the test manager has to assume here? How are the tasks distributed between project manager, test manager and scrum master, if applicable? Which (new) requirements or tasks ensue for the task manager from the target “Continuous Delivery/Deployment”? How to deal with prioritization of tests, selection and management of test data and management of test environments and infrastructure? By use of which metrics the test effort is planned, the test progress traced and the developed software quality evaluated? Which norms and compliance requirements are to be met? How is the quality of supplied software or open source components checked?
- Test methods & Monitoring
To what extent can and should statistical analysis (review, inspection, code analysis) be used in order to detect errors at an early stage and to reduce subsequent test effort? Which tools are at disposal and what can they provide? Which test (design) methods and tools for functional and non-functional (dynamic) tests are used (e.g. combinatorial testing, model-based testing (MBT), fuzzing und search-based testing, test data generating/selection/prioritization/anonymization)? How is the test coverage assessed? Will the systems be monitored during operation after their deployment (quality in use)?
- Test automation & Deployment
Which techniques and tools for test automation (in components, integration or system test) are used? How do they work and what experience has been gained? What experience has been gained from test driven development (TDD, BDD, ATDD etc.)? How and in what circumstances can a successful step towards “Continuous Deployment” or “Continuous Delivery” be made?
- Special Topics
Cross-functional cooperation, DevOps (cooperation development-test-production), training and advanced training of teams, leading of teams, people skills, domain-specific methods/practices (e.g. testing of AI systems, block chain applications etc.).
Contributions can be submitted in the following formats:
- Field report (45 min): Your field report illustrates which changes (either evolutionary or disruptive) have/had to be addressed in your company/your project in order to better intermesh development, test and IT operation. You outline where and how QA and tests are involved and explain which new or changed procedures/methods/techniques/tools have been/will be applied. You discuss which results have been/will be achieved and how the use can be evaluated from a current point of view, which will be achieved in comparison to the previous situation (e.g. risk reduction, quality gain, time gain, cost saving, error prevention, standardization of procedures etc.).
- Tutorial (90 min): Your tutorial presents a certain method (e.g. test-driven development) in detail or deepens a special aspect of the conference topic (e.g. continuous deployment). The participants become familiar with the method in particular, from the theoretical principles up to the practical application of the technique.
- Workshop (80 min): A specific topic will be deepened during your workshop. As a supplement to the tutorial and under your guidance, the workshop format offers the participants an opportunity of practical exercises.
- Solution workshop (45 min): You would like to present your tools, products and services in the context of software quality and software tests? As an exhibitor, you have the opportunity to expressively present your solutions to a qualified target group within the framework of a solution workshop designed by you.
- Software/hardware development managers, IT managers, team leaders benefit from diverse examples of how to further improve procedures and processes.
- Test managers, test leaders, project managers, product owners and scrum masters learn how to design and implement current projects more efficiently.
- Test designers, test automation specialists, testers and developers learn techniques and tools which improve their daily practice
Schedule and prodedure
Please send your contribution with your contact details by May 22, 2018 at the latest via the following web form: www.qs-tag.de/en/call-for-papers-form/. The respective guidelines are to be found on our conference website www.qs-tag.de/en/. The respective Speaker Conditions and Speaker Guidelines are to be found here.
The selection of the contributions will be done by an independent program committee. The notification of your contribution’s acceptance will be given (according to current plans) by June 30, 2018.
Best Paper Award
The best contribution will be awarded with the Software-QS-Tag Best Paper Award.
The evaluation criteria include: content quality, novelty and profundity of the paper handed in as well as the feedback of the conference participants with regard to the quality of the lecture and presentation. At least 5 pages A4 need to be submitted. Submissions with a lower volume are permitted. However, they will not be considered for the Best Paper Award.
The rewarded Best Papers of the recent years can be as examples found here: www.qs-tag.de/en/event-information/best-paper-award/
The exhibition area is limited! Secure your preferred place with an early registration. Please contact us per email to email@example.com.