Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
webapptesting:projects [2009/07/02 21:22] adminwebapptesting:projects [2013/04/20 20:33] (current) – [Development Projects] admin
Line 9: Line 9:
 amounts of information quickly and efficiently.  Therefore, web amounts of information quickly and efficiently.  Therefore, web
 application code is prone to errors and requires effective testing to application code is prone to errors and requires effective testing to
-expose errors.  Testing based on user requests is favorable because+expose errors.  Testing based on user requests is promising because
 user requests are cheap to record and testing focuses on what users user requests are cheap to record and testing focuses on what users
 actually do. In 2005, Sant et al. proposed a promising user-based test actually do. In 2005, Sant et al. proposed a promising user-based test
Line 35: Line 35:
 ====== Development Projects ====== ====== Development Projects ======
  
-  * [[custom_dspace|Customizing DSpace]]+  * [[custom_dspace|Customizing DSpace]] - partially completed during the summer of 2011 
 +  * Adding new functionality to [[logic|Symbolic Logic Tutorial]] for Professor Gregory (Philosophy)
  
-====== Past Undergraduate Research Projects and Their Outcomes ====== 
-  * Developing automated oracle comparators for web applications (led to an ISSRE publication) 
  
-  * Developing WebVizOr, a tool for viewing the HTML results from executing test cases (led to a TAIC-PART publication)+===== NSF Reports ===== 
 + 
 +National Science Foundation grant winners have to submit annual reports to NSF.  The report describes the various activities and results from the past year.  Often winners get to that timeand forget what all they did that year. 
 + 
 +They need way to enter activities, tag them based on the nsf research.gov 
 +categories of where it will get reported in the final report, and any other information 
 +about the task, e.g., when complete, who completed it, how many people involved,... 
 + 
 +Then when they have to write the report, they could search on particular tags for certain date ranges and get a start of a report of activities that they can then just smooth out into paragraphs. 
 + 
 +It would be a web interface that is private to only those people we are 
 +allowed to enter data and create reports, basically the PIs on the grant. 
 + 
 +Categories of activities:  
 +    * education 
 +    * research 
 +    * outreach 
 +    * publications 
 +    * outcomes 
 + 
 +I have an example report, but I don't want to post it online. 
 + 
 +Could use similar fields/information for W&L faculty's Faculty Activity Reports. 
 +====== Past Undergraduate Research Projects and Their Outcomes ====== 
 +  * Analyzing statistical usage-based navigation models for web applications and their resulting test cases (led to an ICST 2011 paper, which received the best research paper award, and an ICST 2012 paper)
    
-  * Developing tools for logging user accesses to Web applications, creating user sessions from the logged accesses, and automatically replaying the generated user sessions and other test cases (used in several publications).+  * Comparing data models for automatically generating test cases for web applications 
 + 
 +  * Developing automated oracle comparators for web applications (led to an ISSRE 2007 publication) 
 + 
 +  * Developing WebVizOr, a tool for viewing the HTML results from executing test cases (led to a TAIC-PART 2008 publication) 
 + 
 +  * Developing tools for logging user accesses to Web applications, creating user sessions from the logged accesses, and automatically replaying the generated user sessions and other test cases (used as part of framework in several publications).
  
   * Customizing an online digital library, which was later used as a subject application in later testing research (included in several publications)   * Customizing an online digital library, which was later used as a subject application in later testing research (included in several publications)
  
   * Mutating Web application code to enable failure detection experiments (led to a GHC poster)   * Mutating Web application code to enable failure detection experiments (led to a GHC poster)
webapptesting/projects.1246569764.txt.gz · Last modified: 2009/10/01 14:46 (external edit)
CC Attribution-Noncommercial-Share Alike 4.0 International
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0