The website is currently being migrated from all sorts of places...local, git page, and work notes...
I was unable to log in to my td online banking site for a few days. The page kept showing that there's a 400s bad request and asked me to try again at a later time.
Tried today with another browser and worked. I realized they must've screwed up the website that the previous local data is no longer compatible with the new site.
Indeed, the error is this :
"Size of a request header field exceeds server limit." (WHAT)
Alas, the mighty chrome has the function to remove individual site data under "privacy->content settings->cookies->see all cookies and site data". But I'm still wondering if the site can force clear client-side cookies though...maybe force the expiration date from the server side?
1. The level of error exposure to users should be accurate and meaningful at the same time.
2. Running with previous settings for compatibility testing needs to be on a regular basis.
3. Messing with data you do not control is BAD.
Had quite a few candidates who had no idea how automation works and how to write automation tests...very sad story...
Thus created this page to use at the interview, to let the candidate write automated tests based on what's on the page.
Planning to add more in the future but this would be sufficient for the upcoming candidates.
Encountered something quite funny when implementing a new webapp...it kept forcing the mobile view even though I'm already requesting for desktop page. I have no idea why this is happening...
Might as well just use this page on the device then...
Found a new tool online today which would help with responsive design testing. This could be a great help for any pages I'd like mobile users to view properly. This is available here.
The app is created based on API available on gecko b2g device. It touches almost all APIs available to the device currently. Eventually this app will be loaded onto an actual device as a vanilla app and will be used to test API status on the specific physical device. Check this out at Firefox OS Webapp.
First thing, we should clone the sugarcrm/PhoneVooDoo repository and check the files under the folder Trio. The powerpoint document is a good starting point to gain some knowledge towards what this piece of code does.
There are some useful links provided in ref#2 to help us understand the whole iOS automation process. Also there's been enhancements done by apple to make our lives easier. We will also want to be able to run trio through command line as well in order to make it friendly for CI automation process. Trio uses documentbuilder for xml parsing, so some knowledge regarding the w3c dom libraries are recommended.
This is available at this github repo.
A software developer currently based in NYC. I love dig around things which makes my time spent worthwhile.