Backstage SQA Days. Guide to action
Dear SQA Days speakers!
Thank you for your work and for seeking to share knowledge with colleagues.
In order for your information to be as useful as possible to the audience and in demand, please read our translation article “ Behind the scenes of EuroSTAR. Or a look at the conference organization by the program committee chairman Michael Bolton, ” this will allow you to more clearly position your report. We share the views of Michael Bolton and all that he says to a large extent applies to all conferences.
')
When submitting a report, answer the following questions:
1. Who is this report for?
Determine your target audience, determine the level of the audience. So it is necessary to submit an entry-level report, because at the conference there will be many people with experience of 2 years or more? You do not need to submit a report for the sake of performance, you need to submit a report in order to share useful knowledge.
2. What can your report give in practice?
Reports are different: general education, systematizing, practical, etc. Determine what your report is and what it will give to the listener. If the listener, having listened to your report, is not able to endure anything for himself, this is obviously a failure. Remember, you are not telling for yourself, but for people who value you. Try to present information in such a way that it is not a special case for you, but so that it can be used or, at least, suggests ideas on how to use it. Systematization of knowledge in some areas is also good, if their practical application is shown.
As a result, more practice, less “water”!
Do not forget that the report must comply with the stated topic and annotations! Do not ignore it!
3. Only the juice!
Do not get carried away advertising your companies. Your competence is the most important advertising. Believe me, if you can competently talk about what you have encountered, you will be asked a lot of questions, including where you work, you will not be released on the sidelines. Here you can tell about the company.
Speaking at the conference, you earn a kind of rating, according to which you will be assessed in the future by both listeners and all other interested parties, including us. Forget about the shovel "shredded" - give everything to the fullest and get pleasure from it.
4. Do not forget to respond to reviewers comments.
In the program committee involved current employees of companies. This means that in addition to the main work, they pay attention to the reports and give feedback. When submitting a report, do not forget to respond to the comments of the program committee, especially since you receive notifications. We ask you to adequately and impartially relate to the opinion of reviewers. Remember - they are your friends and try to help you make the most useful report. It is not necessary to discuss the identity of the members of the program committee, this is a notorious failure. Everything is simple and open with us - “without ponts”.
5. Do not forget to submit reports.
Many are registered as speakers, but there are no reports. Do not forget about the deadlines for submitting reports , as well as about the fact that if a report is not submitted, then there are no preferential conditions for participation in the conference. “Fake” reports will also lead to the fact that they will have to participate on a general basis. Please treat reports with full responsibility. In the end, you demonstrate the face of not only the company, but also your own as a specialist.
6. What to tell?
We do not make restrictions. However, we can designate trends based on opinions from questionnaires from previous conferences (of course, these trends should not be limited):
game dev
- approaches to testing classic software and games.
- what is the difference, what is the similarity?
- How to change the mentality of the tester during the transition to the game development company?
What do you pay attention to in the test object in the usual software?
What began to pay attention in geymdev?
How has the attitude to the life cycle of the system?
How has the tooling changed?
- how to change the mentality of the tester when moving to a classic software company? is there a continuity of knowledge?
- How are game engines tested?
- what are the features of work in an international team? (many games are developed by distant divisions)
automation
- practical and practically applicable (do not forget about the listeners!) Aspects of automation
- Stress Testing
- automation of mobile applications
- game automation
- automation of old applications (about it below)
security
- practical security testing methods
- tester tools
old (not so rare) applications
- at various industrial enterprises, such applications manage the production process: from accounting to inventory management. They are usually supported by the local IT department. There still lives FoxPro, Access. Applications are written under DOS and often do not have a Windows interface at all (often this can be found in banks, where unloading is done on a floppy disk). Or are these desktop applications written in Delphi v.2.0 or CBuilder.
- how to test the update of such applications?
- Is it possible to use modern automation tools?
- features of testing such applications?
- how to build effective support for such applications?
- Do you need to switch to new technologies if the old ones work well?
- the problem of lack of documentation for old systems (all in the minds of the developers of the local IT department)
- the problem of building processes in the introduction of new modern systems
mobile development
- testing applications for the main operating systems Android, iOS, Windows
- application testing for rare and conditionally rare operating systems
- test automation of such applications: features, practice, tools
development of cross-platform applications
- the main nuances of testing applications, complexity, approaches to testing
- tools used
features of testing development for the public sector
- the basic construction of the process of testing applications for the public sector, especially the building of interaction with experts (who is responsible for what)
- building the process of information exchange (how, in what environment, at what level to exchange the necessary information)
- introduction of customers to modern IT tools
- documenting the development
- delivery and implementation
- support
cloud technologies
- architecture of interaction of information storage servers (software managing such architecture) and testing of such architecture
- testing data integrity in case of failures
- data security (why are many still not moved to the clouds?)
We invite everyone to the 15th anniversary SQA Days . It will be awesome ... as always. :)
Thank you for your work and for seeking to share knowledge with colleagues.
In order for your information to be as useful as possible to the audience and in demand, please read our translation article “ Behind the scenes of EuroSTAR. Or a look at the conference organization by the program committee chairman Michael Bolton, ” this will allow you to more clearly position your report. We share the views of Michael Bolton and all that he says to a large extent applies to all conferences.
')
When submitting a report, answer the following questions:
1. Who is this report for?
Determine your target audience, determine the level of the audience. So it is necessary to submit an entry-level report, because at the conference there will be many people with experience of 2 years or more? You do not need to submit a report for the sake of performance, you need to submit a report in order to share useful knowledge.
2. What can your report give in practice?
Reports are different: general education, systematizing, practical, etc. Determine what your report is and what it will give to the listener. If the listener, having listened to your report, is not able to endure anything for himself, this is obviously a failure. Remember, you are not telling for yourself, but for people who value you. Try to present information in such a way that it is not a special case for you, but so that it can be used or, at least, suggests ideas on how to use it. Systematization of knowledge in some areas is also good, if their practical application is shown.
As a result, more practice, less “water”!
Do not forget that the report must comply with the stated topic and annotations! Do not ignore it!
3. Only the juice!
Do not get carried away advertising your companies. Your competence is the most important advertising. Believe me, if you can competently talk about what you have encountered, you will be asked a lot of questions, including where you work, you will not be released on the sidelines. Here you can tell about the company.
Speaking at the conference, you earn a kind of rating, according to which you will be assessed in the future by both listeners and all other interested parties, including us. Forget about the shovel "shredded" - give everything to the fullest and get pleasure from it.
4. Do not forget to respond to reviewers comments.
In the program committee involved current employees of companies. This means that in addition to the main work, they pay attention to the reports and give feedback. When submitting a report, do not forget to respond to the comments of the program committee, especially since you receive notifications. We ask you to adequately and impartially relate to the opinion of reviewers. Remember - they are your friends and try to help you make the most useful report. It is not necessary to discuss the identity of the members of the program committee, this is a notorious failure. Everything is simple and open with us - “without ponts”.
5. Do not forget to submit reports.
Many are registered as speakers, but there are no reports. Do not forget about the deadlines for submitting reports , as well as about the fact that if a report is not submitted, then there are no preferential conditions for participation in the conference. “Fake” reports will also lead to the fact that they will have to participate on a general basis. Please treat reports with full responsibility. In the end, you demonstrate the face of not only the company, but also your own as a specialist.
6. What to tell?
We do not make restrictions. However, we can designate trends based on opinions from questionnaires from previous conferences (of course, these trends should not be limited):
game dev
- approaches to testing classic software and games.
- what is the difference, what is the similarity?
- How to change the mentality of the tester during the transition to the game development company?
What do you pay attention to in the test object in the usual software?
What began to pay attention in geymdev?
How has the attitude to the life cycle of the system?
How has the tooling changed?
- how to change the mentality of the tester when moving to a classic software company? is there a continuity of knowledge?
- How are game engines tested?
- what are the features of work in an international team? (many games are developed by distant divisions)
automation
- practical and practically applicable (do not forget about the listeners!) Aspects of automation
- Stress Testing
- automation of mobile applications
- game automation
- automation of old applications (about it below)
security
- practical security testing methods
- tester tools
old (not so rare) applications
- at various industrial enterprises, such applications manage the production process: from accounting to inventory management. They are usually supported by the local IT department. There still lives FoxPro, Access. Applications are written under DOS and often do not have a Windows interface at all (often this can be found in banks, where unloading is done on a floppy disk). Or are these desktop applications written in Delphi v.2.0 or CBuilder.
- how to test the update of such applications?
- Is it possible to use modern automation tools?
- features of testing such applications?
- how to build effective support for such applications?
- Do you need to switch to new technologies if the old ones work well?
- the problem of lack of documentation for old systems (all in the minds of the developers of the local IT department)
- the problem of building processes in the introduction of new modern systems
mobile development
- testing applications for the main operating systems Android, iOS, Windows
- application testing for rare and conditionally rare operating systems
- test automation of such applications: features, practice, tools
development of cross-platform applications
- the main nuances of testing applications, complexity, approaches to testing
- tools used
features of testing development for the public sector
- the basic construction of the process of testing applications for the public sector, especially the building of interaction with experts (who is responsible for what)
- building the process of information exchange (how, in what environment, at what level to exchange the necessary information)
- introduction of customers to modern IT tools
- documenting the development
- delivery and implementation
- support
cloud technologies
- architecture of interaction of information storage servers (software managing such architecture) and testing of such architecture
- testing data integrity in case of failures
- data security (why are many still not moved to the clouds?)
We invite everyone to the 15th anniversary SQA Days . It will be awesome ... as always. :)
Source: https://habr.com/ru/post/210538/
All Articles