Last Comment Bug 795244 - [dev]Searching by name for a product just created does not return any results
: [dev]Searching by name for a product just created does not return any results
Status: VERIFIED WORKSFORME
:
Product: Mozilla QA
Classification: Other
Component: MozTrap (show other bugs)
: unspecified
: x86_64 Linux
: -- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-28 02:50 PDT by Trif Andrei-Alin[:AlinT]
Modified: 2012-10-01 04:34 PDT (History)
3 users (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Attachments
Creating the product (187.75 KB, image/png)
2012-09-28 02:50 PDT, Trif Andrei-Alin[:AlinT]
no flags Details
Searching for the product (181.90 KB, image/png)
2012-09-28 02:51 PDT, Trif Andrei-Alin[:AlinT]
no flags Details

Description Trif Andrei-Alin[:AlinT] 2012-09-28 02:50:09 PDT
Created attachment 665835 [details]
Creating the product

1.Go to https://moztrap-dev.allizom.org/manage/product/add/
2.Create a product and save it.
3.Search by the name of the product created.

Expected results
Results containing the product should be displayed (or a single result matching the described product)

Actual results:
No results displayed.

*This bug was found due to failure on moztrap-tests suite (TestManageProductsPage.test_that_user_can_filter_product_by_name)
Comment 1 Trif Andrei-Alin[:AlinT] 2012-09-28 02:51:54 PDT
Created attachment 665836 [details]
Searching for the product
Comment 2 Cameron Dawson [:camd] 2012-09-28 17:05:35 PDT
I think the test case may have an error with it.  In the screenshot, it shows a filter for "examplebug" but the name of the existing product is "exampleforbug".  I tried it myself and it works as expected with a new product called "CamTest 0928".

Would you please retest and reopen, in case I missed something?  Thanks!
Comment 3 Trif Andrei-Alin[:AlinT] 2012-10-01 04:34:58 PDT
Yeah, I've made a mistake by attaching the wrong screenshot on friday(had several test cases prepared with different inputs)
But there was a problem on Friday(the automated tests were failing due to it), but now it's gone.
QA verified

Note You need to log in before you can comment on or make changes to this bug.