“…Nowadays, the functionality of many IDEs can be extended with plugins to collect data with additional features, lifting the previous technological restrictions. Examples include student-IDE interactions (Brown, Kolling, McCall, & Utting, 2014;Hundhausen, Olivares, & Carter, 2017), asynchronous discussion posts , automatic testing against test cases (Edwards & Perez-Quinones, 2008), survey/quiz data to gain insights into learner attitudes and conceptual understanding of tasks (Ihantola, Sorva, & Vihavainen, 2014), studies collecting data from eye-trackers (Busjahn et al, 2014;Kevic et al, 2015;Mangaroska, Sharma, Giannakos, Traetteberg, & Dillenbourg, 2018), mouse and keyboard pressure (Arapakis, Lalmas, & Valkansas, 2014;Begel, 2016), heart rate (Ahonen et al, 2016), and electro-dermal activity (Müller, 2015). Although data with additional features can help explain how students learn to program, to our knowledge, none of the hardware devices used to collect data from learners engaged in programming tasks is directly integrated with the IDE, which again imposes limitations on the range of data that can be collected.…”