Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page
Demo Data from EDBT 2026 / reviewers in the wild / expert

Snehit Cherian

dblp:241/6272 · DBLP profile ↗
← Back
2ranked-venue papers
0as first author
0since 2021 · last 2019
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 2

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
2 papers
Software testing · 81% Software maintenance and evolution · 19%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Cloud and datacenter computing · 100%

Topics — the 4 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Software testing › regression testing
test case prioritization		 0.412019
TERMINATOR: better automated UI test case prioritization · ESEC/SIGSOFT FSE 2019
Cloud and datacenter computing
cloud service reliability		 0.412019
Predicting breakdowns in cloud services (with SPIKE) · ESEC/SIGSOFT FSE 2019
Software maintenance and evolution › release engineering
continuous integration		 0.112019
TERMINATOR: better automated UI test case prioritization · ESEC/SIGSOFT FSE 2019
Software testing
software reliability		 0.112019
Predicting breakdowns in cloud services (with SPIKE) · ESEC/SIGSOFT FSE 2019

Methods — techniques the papers use, named apart from their topics

time series prediction · 0.8machine learning · 0.8automated UI testing · 0.4
YearPublicationVenuePosition
2019 Predicting breakdowns in cloud services (with SPIKE)
abstract
Maintaining web-services is a mission-critical task where any down- time means loss of revenue and reputation (of being a reliable service provider). In the current competitive web services market, such a loss of reputation causes extensive loss of future revenue.
Joymallya Chakraborty, Philip Clark, Kevin Haverlock, Snehit Cherian, Tim Menzies
 ESEC/SIGSOFT FSE5
2019 TERMINATOR: better automated UI test case prioritization
abstract
Automated UI testing is an important component of the continuous integration process of software development. A modern web-based UI is an amalgam of reports from dozens of microservices written by multiple teams. Queries on a page that opens up another will fail if any of that page's microservices fails. As a result, the overall cost for automated UI testing is high since the UI elements cannot be tested in isolation. For example, the entire automated UI testing suite at LexisNexis takes around 30 hours (3-5 hours on the cloud) to execute, which slows down the continuous integration process.
Zhe Yu 0002, Fahmid M. Fahid, Tim Menzies, Gregg Rothermel, Kyle Patrick, Snehit Cherian
 ESEC/SIGSOFT FSE6