MailNews Talk:Memory Bloat and Leak Tests: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Update now that the main patches are in.)
No edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Bug|458351}} is the master meta bug for tracking improvements.
'''NOTE: This page (and its related content page) has been moved to the [https://developer.mozilla.org/Talk:en/MailNews/Leak_And_Bloat_Tests Mozilla Developer Center]. Please refer to that page for recent updates and discussions.


== Master list for wanted improvements ==
{{Bug|458351}} is the master meta bug for tracking improvements.'''


These are the ones we really want short-term and would like folks to work on. Please put other ideas in the section below.
== Master list for wanted improvements  ==


{|border=1
These are the ones we really want short-term and would like folks to work on. Please put other ideas in the section below.
 
{| border="1"
|-
|-
| Bug || Title || Comments
| Bug  
| Title  
| Comments
|-
|-
| - || GristMill/MozMill integration || GristMill is a tool designed to allow UI automation for testing. It is suited to bloat tests, because it will make it easy to consistently test the UI and we will be able to test the UI is working at the same time as testing leak/bloat.
| {{Bug|458352}}
| GristMill/MozMill integration  
| GristMill is a tool designed to allow UI automation for testing. It is suited to bloat tests, because it will make it easy to consistently test the UI and we will be able to test the UI is working at the same time as testing leak/bloat.
|-
|-
| || SMTP fake server integration - sending messages || We already have a fake server for SMTP in mailnews. Integrating it into our tests will allow checking of the mail sending process (from compose window to server) at a UI level and for leak/bloat.
| {{Bug|458353}}
| SMTP fake server integration - sending messages  
| We already have a fake server for SMTP in mailnews. Integrating it into our tests will allow checking of the mail sending process (from compose window to server) at a UI level and for leak/bloat.
|}
|}


Note: leaving the main wanted improvements to those at the moment. MozMill integration would be the biggest win and provide us with much easier ways of generating tests for the code. Meanwhile getting the appropriate hooks in place for a fake SMTP server and allowing that to run is probably also a reasonable amount of work, but separate to the MozMill integration. --[[User:Standard8|Standard8]] 10:45, 3 October 2008 (UTC)
Note: leaving the main wanted improvements to those at the moment. MozMill integration would be the biggest win and provide us with much easier ways of generating tests for the code. Meanwhile getting the appropriate hooks in place for a fake SMTP server and allowing that to run is probably also a reasonable amount of work, but separate to the MozMill integration. --[[User:Standard8|Standard8]] 10:45, 3 October 2008 (UTC)  
 
== New ideas/Discussion  ==


== New ideas/Discussion ==
=== Predefined Accounts  ===


=== Predefined Accounts ===
Add these to the basic profile  
Add these to the basic profile


* I've added IMAP & NNTP to the future requirements for the profile, as I mentioned in my posting, the initial task is to get some basic data asap. I will try and add these if there is time before I do the tests --[[User:Standard8|Standard8]] 00:34, 9 April 2008 (PDT)
*I've added IMAP & NNTP to the future requirements for the profile, as I mentioned in my posting, the initial task is to get some basic data asap. I will try and add these if there is time before I do the tests --[[User:Standard8|Standard8]] 00:34, 9 April 2008 (PDT)


=== Server support required ===
=== Server support required ===


* IMAP server with a private account which tester controls the mail available.
*IMAP server with a private account which tester controls the mail available.  
* NNTP server with a private group which tester controls and maintains postings.
*NNTP server with a private group which tester controls and maintains postings.


The NNTP requirement can be fulfilled by MoFo creating an athentication controled news group. This has an advantage of verifying the authentication code as well as the additional memory requirements.
The NNTP requirement can be fulfilled by MoFo creating an athentication controled news group. This has an advantage of verifying the authentication code as well as the additional memory requirements.  


* We want a server running on the tinderbox to avoid network problems and latencies. The server would use a consistent data set and wouldn't be changeable from outside. --[[User:Standard8|Standard8]] 00:34, 9 April 2008 (PDT)
*We want a server running on the tinderbox to avoid network problems and latencies. The server would use a consistent data set and wouldn't be changeable from outside. --[[User:Standard8|Standard8]] 00:34, 9 April 2008 (PDT)


=== Interfaces ===
=== Interfaces ===


* NNTP, Port:563 SSL/TLS workout
*NNTP, Port:563 SSL/TLS workout  
* SMTP w/SSL or TLS
*SMTP w/SSL or TLS  
* RSS feed
*RSS feed  
* Lightning CalDav, etc.
*Lightning CalDav, etc.  
* Other Protocols as added
*Other Protocols as added


The more code we open and close will yeald a better simulation of daily use.
The more code we open and close will yeald a better simulation of daily use.  


--[[User:Killjay|Ron K.]] 15:00, 8 April 2008 (PDT)
--[[User:Killjay|Ron K.]] 15:00, 8 April 2008 (PDT)  


Agreed we will need to open up more code once we get the basic tests running day-to-day.
Agreed we will need to open up more code once we get the basic tests running day-to-day. --[[User:Standard8|Standard8]] 00:34, 9 April 2008 (PDT)  
--[[User:Standard8|Standard8]] 00:34, 9 April 2008 (PDT)


=== Miscellaneous ===  
=== Miscellaneous ===


* Large Message folders and selection thereof.
*Large Message folders and selection thereof.  
* Large Address Books.
*Large Address Books.
Confirmed users
371

edits

Navigation menu